From owner-freebsd-arch Thu Jul 6 14:32:38 2000 Delivered-To: freebsd-arch@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 37D1637B798 for ; Thu, 6 Jul 2000 14:32:35 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id B277D1C65; Thu, 6 Jul 2000 17:32:34 -0400 (EDT) Date: Thu, 6 Jul 2000 17:32:34 -0400 From: Bill Fumerola To: Marius Bendiksen Cc: Alfred Perlstein , freebsd-arch@FreeBSD.ORG Subject: Re: Alterations to vops Message-ID: <20000706173234.V4034@jade.chc-chimes.com> References: <20000628231510.F275@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mbendiks@eunet.no on Thu, Jul 06, 2000 at 11:29:26PM +0200 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 06, 2000 at 11:29:26PM +0200, Marius Bendiksen wrote: > > Can you elaborate on the problem you are describing? I'm not sure > > I understand besideds certain processes being able to hog the > > buffercache and filesystems. > > The problem lies, as I understand it (ask Feldman for details) in that a > find(1) or similar process will cause a lot of work to be done in kernel > space, which means the scheduler is not going to clamp down on it. Also, > it apparently hogs buffercache and I/O bandwidth. Changing these VOPs to > be incremental would solve the problem. My systems get to the point of unusability when find(1) or cvsup(1) are running. These things should be getting scheduled way back, but when I hit 'i' in vi, it can take 30 seconds for it to switch to insert mode. These are not wimpy machines either. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message