I've committed an 80% fix for the random seek / write
performance issue. The rest of the fix will come later
when Kirk commits his shared-lock-buffer-cache idea.
I've committed it into -current and will MFC it into
-stable in a week if there aren't any problems. I
do not intend to MFC it into 3.x.
This should solve most of the random-I/O latency issues
with read-after-write on buffers. Basically what
had to be done was to continue to call the clustering
code as before (so reallocblks still gets called), but
only issue write_behind I/O if the writes are
generally sequential. If the writes are random, even
big writes, we do not issue write-behind I/O.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
- Re: patches for test / review Paul Richards
- FreeBSD random I/O performance issues Richard Wendland
- Re: FreeBSD random I/O performance issues Matthew Dillon
- Re: FreeBSD random I/O performance issues Paul Richards
- Re: FreeBSD random I/O performance issues Matthew Dillon
- Re: FreeBSD random I/O performance issues Mike Smith
- Re: FreeBSD random I/O performance issues Matthew Dillon
- Re: FreeBSD random I/O performance issues Julian Elischer
- Re: FreeBSD random I/O performance issues Richard Wendland
- Re: FreeBSD random I/O performance issues Richard Wendland
- Re: FreeBSD random I/O performance issues Matthew Dillon
- Re: FreeBSD random I/O performance issues Sheldon Hearn
- Re: FreeBSD random I/O performance issues Matthew Dillon
- Re: FreeBSD random I/O performance issues Chris Wasser
- Re: patches for test / review Poul-Henning Kamp
- Re: patches for test / review Greg Lehey
- Re: patches for test / review Poul-Henning Kamp
- Re: patches for test / review Wilko Bulte
- Re: patches for test / review Matthew Jacob
- Re: patches for test / review Matthew Dillon
- Re: patches for test / review Wilko Bulte
