Modid: 2.5.x-xfs:slinx:129771a

The errors were benevolent, we flushed the log more than we needed to.

Modid: 2.5.x-xfs:slinx:129745a

Modid: 2.5.x-xfs:slinx:129728a

Modid: 2.5.x-xfs:slinx:129722a

Switch xfs from using a big endian internal representation for
the in memory copy of extents to a host byte order representation.
The internal extents are read in once, then modified seperately
from the on disk ones. Since we search and manipulate the extents
multiple times, it is cheaper to convert them to host byte order
once and then keep them in that format. Worth about 5 to 10%
reduction in cpu time for some loads. Complicated by the fact
that the in memory extents are written out to the log sometimes,
and when expanding extents are used to write out the initial
block of extents.

Modid: 2.5.x-xfs:slinx:129646a

(has been there a couple of years at least)

Modid: 2.5.x-xfs:slinx:128918a

Modid: 2.5.x-xfs:slinx:128887a

Modid: 2.5.x-xfs:slinx:128653a

Modid: 2.5.x-xfs:slinx:129660a

Modid: 2.5.x-xfs:slinx:129574a

Modid: 2.5.x-xfs:slinx:129466a

Modid: 2.5.x-xfs:slinx:129340a

Modid: 2.5.x-xfs:slinx:129315a

Modid: 2.5.x-xfs:slinx:129236a

Modid: 2.5.x-xfs:slinx:129234a

Symlinks are created by default with mode 777 now, old behavior is
still accessible through sysctl through.  Irixsgid mount option
eprecated and it too is still accessible through sysctl.

Modid: 2.5.x-xfs:slinx:129282a

Modid: 2.5.x-xfs:slinx:129235a

Modid: 2.5.x-xfs:slinx:129160a

Modid: 2.5.x-xfs:slinx:129155a

Modid: 2.5.x-xfs:slinx:129132a

Modid: 2.5.x-xfs:slinx:129120a

Modid: 2.5.x-xfs:slinx:129128a

Modid: 2.5.x-xfs:slinx:129126a

Modid: 2.5.x-xfs:slinx:129117a

Modid: 2.5.x-xfs:slinx:129109a

Modid: 2.5.x-xfs:slinx:129079a

Modid: 2.5.x-xfs:slinx:129049a

Modid: 2.5.x-xfs:slinx:128998a

This is a two fold change, first it moves the translation between
linux dev_t and kdev_t up the call stack in xfs and makes the bulk
of xfs work in terms of its on disk dev_t format.  It also cleans
up a few related chunks of code.
   
The other part of the change reworks how we keep the linux inode
contents and the xfs inode fields in sync. A number of places where
we resynced the two have been removed, these were basically
replicating work elsewhere in the filesystem.   We now also ensure
that the inode fields are filled in before calling unlock_new_inode -
there used to be a window.

Finally all the code which hooks together the linux inode and the xfs
inode is brought together as a more coherent whole rather than being
cattered around the inode create path. Most calls to revalidate the
linux inode from the xfs inode are removed.

Modid: 2.5.x-xfs:slinx:128899a 10/02/02

Modid: 2.5.x-xfs:slinx:128913a

Modid: 2.5.x-xfs:slinx:128905a

Modid: 2.5.x-xfs:slinx:128787a

Modid: 2.5.x-xfs:slinx:128691a

Modid: 2.5.x-xfs:slinx:128659a

Modid: 2.5.x-xfs:slinx:128581a

Modid: 2.5.x-xfs:slinx:128571a

into home.transmeta.com:/home/torvalds/v2.5/linux

This patch from Christoph Hellwig removes the kiobuf/kiovec
infrastructure.

This affects three subsystems:

video-buf.c:

   This patch includes an earlier diff from Gerd which converts
    video-buf.c to use get_user_pages() directly.

   Gerd has acked this patch.

LVM1:

   Is now even more broken.

drivers/mtd/devices/blkmtd.c:

   blkmtd is broken by this change.  I contacted Simon Evans, who
   said "I had done a rewrite of blkmtd anyway and just need to convert
   it to BIO.  Feel free to break it in the 2.5 tree, it will force me
   to finish my code."

Neither EVMS nor LVM2 use kiobufs.  The only remaining breakage
of which I am aware is a proprietary MPEG2 streaming module.  It
could use get_user_pages().

From Anton Blanchard.  This fixes a couple of Linux Test Project
failures.

- Returns EBUSY if the caller is trying to invalidate memory which is
  covered by a locked vma.

  The open group say:

  [EBUSY]
          Some or all of the addresses in the range starting
          at addr and continuing for len bytes are locked,
          and MS_INVALIDATE is specified.

- Returns EINVAL if the caller specified both MS_SYNC and MS_ASYNC

  [EINVAL]
          The value of flags is invalid.

  and:

          "Either MS_ASYNC or MS_SYNC is specified, but not both."

CONFIG_LBD was initially hardwired to "on" for testing.  That seems to
have gone OK, so now make it configurable.