From owner-freebsd-current Mon Apr 3 3:35:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5493C37BDAE for ; Mon, 3 Apr 2000 03:35:14 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12c4CE-000IMZ-00; Mon, 03 Apr 2000 12:35:02 +0200 From: Sheldon Hearn To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues In-reply-to: Your message of "Sat, 01 Apr 2000 17:03:24 PST." <200004020103.RAA43602@apollo.backplane.com> Date: Mon, 03 Apr 2000 12:35:02 +0200 Message-ID: <70590.954758102@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message