linux-toradex.git/include/linux/writeback.h, branch v2.6.20.21

throttle_vm_writeout(): don't loop on GFP_NOFS and GFP_NOIO allocations

2007-03-09T18:50:31+00:00

throttle_vm_writeout() is designed to wait for the dirty levels to subside. 
But if the caller holds IO or FS locks, we might be holding up that writeout.

So change it to take a single nap to give other devices a chance to clean some
memory, then return.

Cc: Nick Piggin 
Cc: OGAWA Hirofumi 
Cc: Kumar Gala 
Cc: Pete Zaitcev 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

[PATCH] separate bdi congestion functions from queue congestion functions

2006-10-20T17:26:35+00:00

Separate out the concept of "queue congestion" from "backing-dev congestion".
Congestion is a backing-dev concept, not a queue concept.

The blk_* congestion functions are retained, as wrappers around the core
backing-dev congestion functions.

This proper layering is needed so that NFS can cleanly use the congestion
functions, and so that CONFIG_BLOCK=n actually links.

Cc: "Thomas Maier" 
Cc: "Jens Axboe" 
Cc: Trond Myklebust 
Cc: David Howells 
Cc: Peter Osterlund 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

fix file specification in comments

2006-10-03T21:01:26+00:00

Many files include the filename at the beginning, serveral used a wrong one.

Signed-off-by: Uwe Zeisberger 
Signed-off-by: Adrian Bunk

[PATCH] BLOCK: Dissociate generic_writepages() from mpage stuff [try #6]

2006-09-30T18:52:26+00:00

Dissociate the generic_writepages() function from the mpage stuff, moving its
declaration to linux/mm.h and actually emitting a full implementation into
mm/page-writeback.c.

The implementation is a partial duplicate of mpage_writepages() with all BIO
references removed.

It is used by NFS to do writeback.

Signed-Off-By: David Howells 
Signed-off-by: Jens Axboe

[PATCH] call mm/page-writeback.c:set_ratelimit() when new pages are hot-added

2006-09-29T16:18:22+00:00

ratelimit_pages in page-writeback.c is recalculated (in set_ratelimit())
every time a CPU is hot-added/removed.  But this value is not recalculated
when new pages are hot-added.

This patch fixes that problem by calling set_ratelimit() when new pages
are hot-added.

[akpm@osdl.org: cleanups]
Signed-off-by: Chandra Seetharaman 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] mm: balance dirty pages

2006-09-26T15:48:44+00:00

Now that we can detect writers of shared mappings, throttle them.  Avoids OOM
by surprise.

Signed-off-by: Peter Zijlstra 
Cc: Hugh Dickins 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Add a real API for dealing with blk_congestion_wait()

2006-09-23T03:24:54+00:00

Signed-off-by: Trond Myklebust

[PATCH] writeback: fix range handling

2006-06-23T14:42:49+00:00

When a writeback_control's `start' and `end' fields are used to
indicate a one-byte-range starting at file offset zero, the required
values of .start=0,.end=0 mean that the ->writepages() implementation
has no way of telling that it is being asked to perform a range
request.  Because we're currently overloading (start == 0 && end == 0)
to mean "this is not a write-a-range request".

To make all this sane, the patch changes range of writeback_control.

So caller does: If it is calling ->writepages() to write pages, it
sets range (range_start/end or range_cyclic) always.

And if range_cyclic is true, ->writepages() thinks the range is
cyclic, otherwise it just uses range_start and range_end.

This patch does,

    - Add LLONG_MAX, LLONG_MIN, ULLONG_MAX to include/linux/kernel.h
      -1 is usually ok for range_end (type is long long). But, if someone did,

		range_end += val;		range_end is "val - 1"
		u64val = range_end >> bits;	u64val is "~(0ULL)"

      or something, they are wrong. So, this adds LLONG_MAX to avoid nasty
      things, and uses LLONG_MAX for range_end.

    - All callers of ->writepages() sets range_start/end or range_cyclic.

    - Fix updates of ->writeback_index. It seems already bit strange.
      If it starts at 0 and ended by check of nr_to_write, this last
      index may reduce chance to scan end of file.  So, this updates
      ->writeback_index only if range_cyclic is true or whole-file is
      scanned.

Signed-off-by: OGAWA Hirofumi 
Cc: Nathan Scott 
Cc: Anton Altaparmakov 
Cc: Steven French 
Cc: "Vladimir V. Saveliev" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] balance_dirty_pages_ratelimited: take nr_pages arg

2006-03-24T15:33:26+00:00

Modify balance_dirty_pages_ratelimited() so that it can take a
number-of-pages-which-I-just-dirtied argument.  For msync().

Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] Represent dirty_*_centisecs as jiffies internally

2006-03-24T15:33:20+00:00

Make that the internal values for:

/proc/sys/vm/dirty_writeback_centisecs
/proc/sys/vm/dirty_expire_centisecs

are stored as jiffies instead of centiseconds.  Let the sysctl interface do
the conversions with full precision using clock_t_to_jiffies, instead of
doing overflow-sensitive on-the-fly conversions every time the values are
used.

Cons: apparent precision loss if HZ is not a multiple of 100, because of
conversion back and forth.  This is a common problem for all sysctl values
that use proc_dointvec_userhz_jiffies.  (There is only one other in-tree
use, in net/core/neighbour.c.)

Signed-off-by: Bart Samwel 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds