The current writer throttling in balance_dirty_pages() assumes that the
writer will be effectively throttled on request queues.

That works fine when the amount of data which can be placed into a
queue is "much less than" total memory.

But if the machine has a small amount of memory, or many disks, or has
large request queues, or large requests, it can go wrong.

For example, with mem=96m and dirty_async_ratio=15, we want to be able
to clamp dirty+writeback memory at 15 megabytes.  But it doesn't work,
because a single SCSI request queue can hold 40 megs or more.  The
heavy writer keeps on dirtying memory until that queue fills up.

So add a test for that - if we did some writeback, and we're *still*
over the dirty+writeback threshold then make the caller take an
explicit nap on some writes terminating.  And keep on doing that until
the dirty+writeback memory subsides.

Software suspend needs a way of forcing page reclaim, up to the point
where 50% of memory is free.

This patch implements a function to do that:

	int shrink_all_memory(int nr_pages);

Will attempt to reclaim `nr_pages' pages and return them to the free
pages pool.  It returns the number of pages which it actually freed.

If called with a "large" number of pages it will only free up to a few
hundred, so the caller needs to loop on it.

If it returns zero then there is no point in calling it again.

Patch from Badari Pulavarty

There was a corner case in the conversion of direct-io to use
bio_add_page() where we would start a new page out at the wrong sector
number.

Fix that by explicitly passing in the current page's starting sector,
and use that in the new BIO if we have to open a new one.

Fix an error-path page->count leak in dio_bio_add_page().

The patch from Rohit and David M-T changes the hugetlb page info in
/proc/meminfo slightly.

It makes the identifiers a little clearer while ensuring that we don't
add any identifiers which have whitespace.  glibc is/shall be parsing
this information to determine the size and alignment requirements of
the hugetlb pages.

This basically means that procfs is a requirement for successful
hugetlb page usage.  Not very nice, but I suspect real-world userspace
fails without procfs anyway.

- drivers/char/n_r3964.c does not compile.  r3964_open() is doing an
  INIT_LIST_HEAD() on a timer->list.  But timer's don't have a `list'
  any more.

  Do an init_timer() instead.

I'm getting a compile failure in scsi_syms.c because it doesn't know
about the new scsi_set_medium_removal().

I'm suprised that this didn't cause errors for more people -- a
MODE_SENSE request for 128 bytes with a stated buffer length of 24
bytes.

Fix: Make the buffer length match the size of the request.

This patch fixes a typo introduced by my last patch to dv1394.

This adds the dmask option. Yes, the dmask option is the permission
bitmask for directory.

This adds fat_show_options() to fat. And instead, this doesn't output
the charset name in fat_fill_super().

This removes the posix option of vfat. The current posix options works
only as an alias of name_check=s.

This merges parse_options() of fat and parse_options() of vfat.
And this doesn't recognize the unknown options.

This fixes the error code which fat_fill_super() returns.

 - Cleanup (purge) some of our old compat code (never thouched)
 - Fix dv1394 compilation warnings without devfs
 - Added new config-rom handling features. Allows for on-the-fly
   config-rom generation for dynamic functionality of the host nodes.
 - Convert to workqueue from taskqueue interfaces. This is actually
   abstracted compatibility code between tqueue/workqueue.

To my suprise a lot of big site/beowulf type people all really want this
diff, which I'd otherwise filed as 'interesting but not important'

(someone really needs to indent the cpqfc driver!)

The _ isnt allowed in a docbook id

of gcc incorrectly accepted as "short". It got fixed to __u8, but
it really should be __u16.