28 Sep, 2006
2 commits
-
SGI-PV: 955302
SGI-Modid: xfs-linux-melb:xfs-kern:26907aSigned-off-by: Nathan Scott
Signed-off-by: Tim Shimmin -
semantics.
SGI-PV: 954580
SGI-Modid: xfs-linux-melb:xfs-kern:26563aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott
Signed-off-by: Tim Shimmin
20 Jun, 2006
1 commit
-
pure bloat.
SGI-PV: 952969
SGI-Modid: xfs-linux-melb:xfs-kern:26251aSigned-off-by: Nathan Scott
09 Jun, 2006
5 commits
-
porters.
SGI-PV: 953338
SGI-Modid: xfs-linux-melb:xfs-kern:26108aSigned-off-by: Nathan Scott
-
SGI-PV: 953338
SGI-Modid: xfs-linux-melb:xfs-kern:26107aSigned-off-by: Nathan Scott
-
SGI-PV: 9533338
SGI-Modid: xfs-linux-melb:xfs-kern:26106aSigned-off-by: Nathan Scott
-
shutdown vop flags consistent with sync vop flags declarations too.
SGI-PV: 939911
SGI-Modid: xfs-linux-melb:xfs-kern:26096aSigned-off-by: Nathan Scott
-
the range spanned by modifications to the in-core extent map. Add
XFS_BUNMAPI() and XFS_SWAP_EXTENTS() macros that call xfs_bunmapi() and
xfs_swap_extents() via the ioops vector. Change all calls that may modify
the in-core extent map for the data fork to go through the ioops vector.
This allows a cache of extent map data to be kept in sync.SGI-PV: 947615
SGI-Modid: xfs-linux-melb:xfs-kern:209226aSigned-off-by: Olaf Weber
Signed-off-by: Nathan Scott
31 Mar, 2006
1 commit
-
SGI-PV: 951299
SGI-Modid: xfs-linux-melb:xfs-kern:25632aSigned-off-by: Nathan Scott
29 Mar, 2006
1 commit
-
these typos.
SGI-PV: 904196
SGI-Modid: xfs-linux-melb:xfs-kern:25539aSigned-off-by: Nathan Scott
14 Mar, 2006
5 commits
-
SGI-PV: 950556
SGI-Modid: xfs-linux-melb:xfs-kern:25377aSigned-off-by: Nathan Scott
-
a preēmpt counter overflow at 256p and above. Change the exclusion
mechanism to use atomic bit operations and busy wait loops to emulate the
spin lock exclusion mechanism but without the preempt count issues.SGI-PV: 950027
SGI-Modid: xfs-linux-melb:xfs-kern:25338aSigned-off-by: David Chinner
Signed-off-by: Nathan Scott -
registering a notifier callback that listens to CPU up/down events to
modify the counters appropriately.SGI-PV: 949726
SGI-Modid: xfs-linux-melb:xfs-kern:25214aSigned-off-by: David Chinner
Signed-off-by: Nathan Scott -
threads, the incore superblock lock becomes the limiting factor for
buffered write throughput. Make the contended fields in the incore
superblock use per-cpu counters so that there is no global lock to limit
scalability.SGI-PV: 946630
SGI-Modid: xfs-linux-melb:xfs-kern:25106aSigned-off-by: David Chinner
Signed-off-by: Nathan Scott -
actually use it. Kill this dead code. Signed-off-by: Christoph Hellwig
SGI-PV: 904196
SGI-Modid: xfs-linux-melb:xfs-kern:25086aSigned-off-by: Nathan Scott
11 Jan, 2006
2 commits
-
finally.
SGI-PV: 947038
SGI-Modid: xfs-linux-melb:xfs-kern:24866aSigned-off-by: Nathan Scott
-
consistent.
SGI-PV: 941645
SGI-Modid: xfs-linux-melb:xfs-kern:202961aSigned-off-by: Nathan Scott
10 Jan, 2006
1 commit
-
This patch switches XFS over to use the new mutex code directly as
opposed to the previous workaround patch I posted earlier that avoided
the namespace clash by forcing it back to semaphores. This falls in the
'works for me' category.Signed-off-by: Jes Sorensen
Signed-off-by: Ingo Molnar
02 Nov, 2005
9 commits
-
SGI-PV: 937127
SGI-Modid: xfs-linux:xfs-kern:24201aSigned-off-by: Nathan Scott
-
SGI-PV: 943866
SGI-Modid: xfs-linux:xfs-kern:24030aSigned-off-by: Nathan Scott
-
boilerplate.
SGI-PV: 913862
SGI-Modid: xfs-linux:xfs-kern:23903aSigned-off-by: Nathan Scott
-
SGI-PV: 943122
SGI-Modid: xfs-linux:xfs-kern:23901aSigned-off-by: Nathan Scott
-
/proc/mounts.
SGI-PV: 942984
SGI-Modid: xfs-linux:xfs-kern:23862aSigned-off-by: Nathan Scott
-
the data/attr forks now grow up/down from either end of the literal area,
rather than dividing the literal area into two chunks and growing both
upward. Means we can now make much more efficient use of the attribute
space, incl. fitting DMF attributes inline in 256 byte inodes, and large
jumps in dbench3 performance numbers. It is self enabling, but can be
forced on/off via the attr2/noattr2 mount options.SGI-PV: 941645
SGI-Modid: xfs-linux:xfs-kern:23837aSigned-off-by: Nathan Scott
-
filesystems to expose the filesystem stripe width in stat(2) rather than
the page cache size. This allows applications requiring high bandwidth to
easily determine the optimum I/O size for the underlying filesystem. The
default is to report the page cache size (i.e. "nolargeio").SGI-PV: 942818
SGI-Modid: xfs-linux:xfs-kern:23830aSigned-off-by: David Chinner
Signed-off-by: Nathan Scott -
SGI-PV: 942815
SGI-Modid: xfs-linux:xfs-kern:23829aSigned-off-by: Nathan Scott
-
writes. In addition flush the disk cache on fsync if the sync cached
operation didn't sync the log to disk (this requires some additional
bookeping in the transaction and log code). If the device doesn't claim to
support barriers, the filesystem has an extern log volume or the trial
superblock write with barriers enabled failed we disable barriers and
print a warning. We should probably fail the mount completely, but that
could lead to nasty boot failures for the root filesystem. Not enabled by
default yet, needs more destructive testing first.SGI-PV: 912426
SGI-Modid: xfs-linux:xfs-kern:198723aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott
21 Jun, 2005
2 commits
-
SGI-PV: 932952
SGI-Modid: xfs-linux:xfs-kern:22805aSigned-off-by: Nathan Scott
-
SGI-PV: 936255
SGI-Modid: xfs-linux:xfs-kern:192760aSigned-off-by: Christoph Hellwig
Signed-off-by: Nathan Scott
06 May, 2005
3 commits
-
SGI Modid: xfs-linux:xfs-kern:22378a
Signed-off-by: Nathan Scott
Signed-off-by: Christoph Hellwig -
…ed the offset originally requested. Can cause data corruption when multiple processes are performing writeout on different areas of the same file. Quite difficult to hit though.
SGI Modid: xfs-linux:xfs-kern:22377a
Signed-off-by: Nathan Scott <nathans@sgi.com>
Signed-off-by: Christoph Hellwig <hch@sgi.com>
. -
SGI Modid: xfs-linux:xfs-kern:22261a
Signed-off-by: Nathan Scott
Signed-off-by: Christoph Hellwig
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!