From owner-freebsd-hackers Thu Jun 18 17:00:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11450 for freebsd-hackers-outgoing; Thu, 18 Jun 1998 17:00:14 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fs2.ny.genx.net (fs2.ny.genx.net [206.64.4.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11402 for ; Thu, 18 Jun 1998 17:00:08 -0700 (PDT) (envelope-from perlsta@fs2.ny.genx.net) Received: from localhost (perlsta@localhost) by fs2.ny.genx.net (8.8.8/8.8.5) with SMTP id TAA11008; Thu, 18 Jun 1998 19:57:46 -0400 (EDT) Date: Thu, 18 Jun 1998 19:57:45 -0400 (EDT) From: Alfred To: spork cc: hackers@FreeBSD.ORG Subject: Re: Disk Cache In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you could mount "sync", the problem with this is that there will still be read buffers for cached read data, however you can try it. in fact it's kinda good that it will keep buffers available for reading because then you don't have to hit the interface all that much and do memory to memory copying or dma requests... -Alfred On Thu, 18 Jun 1998, spork wrote: > Hi, > > I have a question about FBSD's disk cache mechanism. What happens when > you run a SCSI-SCSI raid controller that contains it's own cache memory? > The kernel has no way of knowing that some things are already cached out > beyond the SCSI card, so I assume it would cache something that's already > cached, right? How do you work around that? Is there some way of telling > it "hey, don't be very aggressive with your disk caching"? Or is it such > a low priority thing that memory isn't used for cache unless there's no > other use for it? > > Thanks, > > Charles > > Charles Sprickman > spork@super-g.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message