litmus-rt.git - The LITMUS^RT kernel.

The LITMUS^RT kernel.

Bjoern Brandenburg

about summary refs log tree commit diff stats

diff options

author	Tushar Behera <tushar.behera@linaro.org>	2012-03-09 11:03:13 -0500
committer	Kukjin Kim <kgene.kim@samsung.com>	2012-03-09 11:03:13 -0500
commit	4db17215da33940e4c594c1152ce765c5506a621 (patch)
tree	a416c0943f6bde5ccb365e094fba55d4f207c93d /net/lapb/lapb_out.c
parent	7f471ee8bed570c0f8ea48f17a957c3b31f54a61 (diff)

ARM: SAMSUNG: Add __init attribute to samsung_bl_set()

s3c_set_platdata() is defined with __init attribute, hence all functions referencing this function should also be defined with __init attribute. samsung_bl_set() is referenced only in '__init xxx_machine_init()' functions, thus this change won't put any additional constraint on the usage of samsung_bl_set(). Signed-off-by: Tushar Behera <tushar.behera@linaro.org> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>

Diffstat (limited to 'net/lapb/lapb_out.c')

0 files changed, 0 insertions, 0 deletions

m"> * 3. DIRECT - the number of bytes read or written from files * opened with the O_DIRECT flag. * * These counters give a view of the data throughput into and out * of the NFS client. Comparing the number of bytes requested by * an application with the number of bytes the client requests from * the server can provide an indication of client efficiency * (per-op, cache hits, etc). * * These counters can also help characterize which access methods * are in use. DIRECT by itself shows whether there is any O_DIRECT * traffic. NORMAL + DIRECT shows how much data is going through * the system call interface. A large amount of SERVER traffic * without much NORMAL or DIRECT traffic shows that applications * are using mapped files. * * NFS page counters * * These count the number of pages read or written via nfs_readpage(), * nfs_readpages(), or their write equivalents. * * NB: When adding new byte counters, please include the measured * units in the name of each byte counter to help users of this * interface determine what exactly is being counted. */ enum nfs_stat_bytecounters { NFSIOS_NORMALREADBYTES = 0, NFSIOS_NORMALWRITTENBYTES, NFSIOS_DIRECTREADBYTES, NFSIOS_DIRECTWRITTENBYTES, NFSIOS_SERVERREADBYTES, NFSIOS_SERVERWRITTENBYTES, NFSIOS_READPAGES, NFSIOS_WRITEPAGES, __NFSIOS_BYTESMAX, }; /* * NFS event counters * * These counters provide a low-overhead way of monitoring client * activity without enabling NFS trace debugging. The counters * show the rate at which VFS requests are made, and how often the * client invalidates its data and attribute caches. This allows * system administrators to monitor such things as how close-to-open * is working, and answer questions such as "why are there so many * GETATTR requests on the wire?" * * They also count anamolous events such as short reads and writes, * silly renames due to close-after-delete, and operations that * change the size of a file (such operations can often be the * source of data corruption if applications aren't using file * locking properly). */ enum nfs_stat_eventcounters { NFSIOS_INODEREVALIDATE = 0, NFSIOS_DENTRYREVALIDATE, NFSIOS_DATAINVALIDATE, NFSIOS_ATTRINVALIDATE, NFSIOS_VFSOPEN, NFSIOS_VFSLOOKUP, NFSIOS_VFSACCESS, NFSIOS_VFSUPDATEPAGE, NFSIOS_VFSREADPAGE, NFSIOS_VFSREADPAGES, NFSIOS_VFSWRITEPAGE, NFSIOS_VFSWRITEPAGES, NFSIOS_VFSGETDENTS, NFSIOS_VFSSETATTR, NFSIOS_VFSFLUSH, NFSIOS_VFSFSYNC, NFSIOS_VFSLOCK, NFSIOS_VFSRELEASE, NFSIOS_CONGESTIONWAIT, NFSIOS_SETATTRTRUNC, NFSIOS_EXTENDWRITE, NFSIOS_SILLYRENAME, NFSIOS_SHORTREAD, NFSIOS_SHORTWRITE, NFSIOS_DELAY, __NFSIOS_COUNTSMAX, }; /* * NFS local caching servicing counters */ enum nfs_stat_fscachecounters { NFSIOS_FSCACHE_PAGES_READ_OK, NFSIOS_FSCACHE_PAGES_READ_FAIL, NFSIOS_FSCACHE_PAGES_WRITTEN_OK, NFSIOS_FSCACHE_PAGES_WRITTEN_FAIL, NFSIOS_FSCACHE_PAGES_UNCACHED, __NFSIOS_FSCACHEMAX, }; #endif /* _LINUX_NFS_IOSTAT */


context:
space:
mode: