An error occurred fetching the project authors.
- 07 Apr, 2003 1 commit
-
-
Christoph Hellwig authored
[XFS] remove busy inode check in the umount path - Linux checked it for us before calling into the filesystem. We're beyond the point of no return for umount anyway SGI Modid: 2.5.x-xfs:slinx:142731a
-
- 26 Mar, 2003 1 commit
-
-
Nathan Scott authored
SGI Modid: 2.5.x-xfs:slinx:141925a
-
- 14 Jan, 2003 3 commits
-
-
Christoph Hellwig authored
SGI Modid: 2.5.x-xfs:slinx:136795a
-
Russell Cattelan authored
apparently the root file system are not being synced correctly during system shutdown SGI Modid: 2.5.x-xfs:slinx:136269a
-
Eric Sandeen authored
SGI Modid: 2.5.x-xfs:slinx:135881a
-
- 06 Nov, 2002 2 commits
-
-
Christoph Hellwig authored
SGI Modid: 2.5.x-xfs:slinx:131130a
-
Nathan Scott authored
longer needs to be declared globally here. SGI Modid: 2.5.x-xfs:slinx:130827a
-
- 15 Oct, 2002 4 commits
-
-
Stephen Lord authored
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
-
Christoph Hellwig authored
Modid: 2.5.x-xfs:slinx:129236a
-
Christoph Hellwig authored
Modid: 2.5.x-xfs:slinx:129234a
-
Stephen Lord authored
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
-
- 26 Sep, 2002 1 commit
-
-
Eric Sandeen authored
Modid: 2.5.x-xfs:slinx:128363a
-
- 11 Sep, 2002 1 commit
-
-
Christoph Hellwig authored
-