From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from penguin.e-mind.com (penguin.e-mind.com [195.223.140.120]) by kvack.org (8.8.7/8.8.7) with ESMTP id RAA28597 for ; Thu, 14 Jan 1999 17:43:38 -0500 Date: Thu, 14 Jan 1999 23:38:31 +0100 (CET) From: Andrea Arcangeli Reply-To: Andrea Arcangeli Subject: Re: MM deadlock [was: Re: arca-vm-8...] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: Mike Jagdis Cc: Alan Cox , "Stephen C. Tweedie" , linux-kernel@vger.rutgers.edu, linux-mm@kvack.org, Alessandro Suardi List-ID: On Thu, 14 Jan 1999, Mike Jagdis wrote: > With either the shm used is normally "large" with respect to > available physical memory (i.e. everything that isn't needed by > processes under your normal load) because the database engines > use it to cache data (this is why they want raw IO - there's no > point the OS caching the data as well). Ah but if what you say is true the db server shm issue raised by Stephen is completly pointless. If the shm memory is used as _cache_ for the data there's _no_ one point to swapout it out in first place. So when using the shm for caching purposes the db server _must_ set the SHM_LOCK flag on the shm memory using shmctl. Andrea Arcangeli -- This is a majordomo managed list. To unsubscribe, send a message with the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org