On Sat, 01 Apr 2000 17:03:24 PST, Matthew Dillon wrote: > 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. Hi Matt, I'd like to suggest that a week is not enough. Given that we seem to be back on the bleeding edge in CURRENT, a lot of folks who might be able to send valuable feedback are less likely to manage a system update within the short space of 1 week. I'm not telling you what to do. I'm just mentioning it in case you'd overlooked the fact that acceptable MFC times grew abnormally short small during the code slush and freeze. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- 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
- Re: patches for test / review Matthew Dillon