From owner-freebsd-hackers Thu Jun 18 14:44:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20746 for freebsd-hackers-outgoing; Thu, 18 Jun 1998 14:44:15 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20711 for ; Thu, 18 Jun 1998 14:44:09 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id RAA18632 for ; Thu, 18 Jun 1998 17:44:10 -0400 (EDT) Date: Thu, 18 Jun 1998 17:44:10 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: hackers@FreeBSD.ORG Subject: Disk Cache 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 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