Merge tag 'v3.1-rc10' into drm-core-next

What:		/sys/class/scsi_host/hostX/isci_id

Date:		June 2011

Contact:	Dave Jiang <dave.jiang@intel.com>

Description:

		This file contains the enumerated host ID for the Intel

		SCU controller. The Intel(R) C600 Series Chipset SATA/SAS

		Storage Control Unit embeds up to two 4-port controllers in

		a single PCI device.  The controllers are enumerated in order

		which usually means the lowest number scsi_host corresponds

		with the first controller, but this association is not

		guaranteed.  The 'isci_id' attribute unambiguously identifies

		the controller index: '0' for the first controller,

		'1' for the second.

5.2 stat file

5.2.1 memory.stat file includes following statistics

memory.stat file includes following statistics

# per-memory cgroup local status

cache		- # of bytes of page cache memory.

	 file_mapped is accounted only when the memory cgroup is owner of page

	 cache.)

5.2.2 memory.vmscan_stat

memory.vmscan_stat includes statistics information for memory scanning and

freeing, reclaiming. The statistics shows memory scanning information since

memory cgroup creation and can be reset to 0 by writing 0 as

 #echo 0 > ../memory.vmscan_stat

This file contains following statistics.

[param]_[file_or_anon]_pages_by_[reason]_[under_heararchy]

[param]_elapsed_ns_by_[reason]_[under_hierarchy]

For example,

  scanned_file_pages_by_limit indicates the number of scanned

  file pages at vmscan.

Now, 3 parameters are supported

  scanned - the number of pages scanned by vmscan

  rotated - the number of pages activated at vmscan

  freed   - the number of pages freed by vmscan

If "rotated" is high against scanned/freed, the memcg seems busy.

Now, 2 reason are supported

  limit - the memory cgroup's limit

  system - global memory pressure + softlimit

           (global memory pressure not under softlimit is not handled now)

When under_hierarchy is added in the tail, the number indicates the

total memcg scan of its children and itself.

elapsed_ns is a elapsed time in nanosecond. This may include sleep time

and not indicates CPU usage. So, please take this as just showing

latency.

Here is an example.

# cat /cgroup/memory/A/memory.vmscan_stat

scanned_pages_by_limit 9471864

scanned_anon_pages_by_limit 6640629

scanned_file_pages_by_limit 2831235

rotated_pages_by_limit 4243974

rotated_anon_pages_by_limit 3971968

rotated_file_pages_by_limit 272006

freed_pages_by_limit 2318492

freed_anon_pages_by_limit 962052

freed_file_pages_by_limit 1356440

elapsed_ns_by_limit 351386416101

scanned_pages_by_system 0

scanned_anon_pages_by_system 0

scanned_file_pages_by_system 0

rotated_pages_by_system 0

rotated_anon_pages_by_system 0

rotated_file_pages_by_system 0

freed_pages_by_system 0

freed_anon_pages_by_system 0

freed_file_pages_by_system 0

elapsed_ns_by_system 0

scanned_pages_by_limit_under_hierarchy 9471864

scanned_anon_pages_by_limit_under_hierarchy 6640629

scanned_file_pages_by_limit_under_hierarchy 2831235

rotated_pages_by_limit_under_hierarchy 4243974

rotated_anon_pages_by_limit_under_hierarchy 3971968

rotated_file_pages_by_limit_under_hierarchy 272006

freed_pages_by_limit_under_hierarchy 2318492

freed_anon_pages_by_limit_under_hierarchy 962052

freed_file_pages_by_limit_under_hierarchy 1356440

elapsed_ns_by_limit_under_hierarchy 351386416101

scanned_pages_by_system_under_hierarchy 0

scanned_anon_pages_by_system_under_hierarchy 0

scanned_file_pages_by_system_under_hierarchy 0

rotated_pages_by_system_under_hierarchy 0

rotated_anon_pages_by_system_under_hierarchy 0

rotated_file_pages_by_system_under_hierarchy 0

freed_pages_by_system_under_hierarchy 0

freed_anon_pages_by_system_under_hierarchy 0

freed_file_pages_by_system_under_hierarchy 0

elapsed_ns_by_system_under_hierarchy 0

5.3 swappiness

Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.

All Sysfs entries are named with their core_id (represented here by 'X').

tempX_input	 - Core temperature (in millidegrees Celsius).

tempX_max	 - All cooling devices should be turned on (on Core2).

		   Initialized with IA32_THERM_INTERRUPT. When the CPU

		   temperature reaches this temperature, an interrupt is

		   generated and tempX_max_alarm is set.

tempX_max_hyst   - If the CPU temperature falls below than temperature,

		   an interrupt is generated and tempX_max_alarm is reset.

tempX_max_alarm  - Set if the temperature reaches or exceeds tempX_max.

		   Reset if the temperature drops to or below tempX_max_hyst.

tempX_crit	 - Maximum junction temperature (in millidegrees Celsius).

tempX_crit_alarm - Set when Out-of-spec bit is set, never clears.

		   Correct CPU operation is no longer guaranteed.

		   number. For Package temp, this will be "Physical id Y",

		   where Y is the package number.

The TjMax temperature is set to 85 degrees C if undocumented model specific

register (UMSR) 0xee has bit 30 set. If not the TjMax is 100 degrees C as

(sometimes) documented in processor datasheet.

On CPU models which support it, TjMax is read from a model-specific register.

On other models, it is set to an arbitrary value based on weak heuristics.

If these heuristics don't work for you, you can pass the correct TjMax value

as a module parameter (tjmax).

Appendix A. Known TjMax lists (TBD):

Some information comes from ark.intel.com

			Override pmtimer IOPort with a hex value.

			e.g. pmtmr=0x508

	pnp.debug	[PNP]

			Enable PNP debug messages.  This depends on the

			CONFIG_PNP_DEBUG_MESSAGES option.

	pnp.debug=1	[PNP]

			Enable PNP debug messages (depends on the

			CONFIG_PNP_DEBUG_MESSAGES option).  Change at run-time

			via /sys/module/pnp/parameters/debug.  We always show

			current resource usage; turning this on also shows

			possible settings and some assignment information.

	pnpacpi=	[ACPI]

			{ off }

			functions are at fixed addresses, they make nice

			targets for exploits that can control RIP.

			emulate     [default] Vsyscalls turn into traps and are

			            emulated reasonably safely.

			emulate     Vsyscalls turn into traps and are emulated

			            reasonably safely.

			native      Vsyscalls are native syscall instructions.

			native      [default] Vsyscalls are native syscall

			            instructions.

			            This is a little bit faster than trapping

			            and makes a few dynamic recompilers work

			            better than they would in emulation mode.

Note: This driver doesn't have a maintainer.

Davicom DM9102(A)/DM9132/DM9801 fast ethernet driver for Linux.

This program is free software; you can redistribute it and/or

Authors:

Sten Wang <sten_wang@davicom.com.tw >   : Original Author

Tobias Ringstrom <tori@unhappy.mine.nu> : Current Maintainer

Contributors: