sysfs « fs - litmus-rt-tegra.git - LITMUS^RT and MC^2 V0 support for the NVIDIA Tegra 3 SoC

about summary refs log tree commit diff stats

Mode	Name	Size
-rw-r--r--	Kconfig	998	log stats plain blame
-rw-r--r--	Makefile	119	log stats plain blame
-rw-r--r--	bin.c	10980	log stats plain blame
-rw-r--r--	dir.c	22717	log stats plain blame
-rw-r--r--	file.c	19380	log stats plain blame
-rw-r--r--	group.c	5425	log stats plain blame
-rw-r--r--	inode.c	8618	log stats plain blame
-rw-r--r--	mount.c	4587	log stats plain blame
-rw-r--r--	symlink.c	7285	log stats plain blame
-rw-r--r--	sysfs.h	6452	log stats plain blame

that has been done writes_starved number of times, we dispatch some writes based on the same criteria as reads. front_merges (bool) ------------ Sometimes it happens that a request enters the io scheduler that is contiguous with a request that is already on the queue. Either it fits in the back of that request, or it fits at the front. That is called either a back merge candidate or a front merge candidate. Due to the way files are typically laid out, back merges are much more common than front merges. For some work loads, you may even know that it is a waste of time to spend any time attempting to front merge requests. Setting front_merges to 0 disables this functionality. Front merges may still occur due to the cached last_merge hint, but since that comes at basically 0 cost we leave that on. We simply disable the rbtree front sector lookup when the io scheduler merge function is called. Nov 11 2002, Jens Axboe <jens.axboe@oracle.com>