From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755991AbYDGVBy (ORCPT ); Mon, 7 Apr 2008 17:01:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752111AbYDGVBq (ORCPT ); Mon, 7 Apr 2008 17:01:46 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:44851 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751504AbYDGVBp (ORCPT ); Mon, 7 Apr 2008 17:01:45 -0400 Message-ID: <47FA8B5A.5090104@cs.helsinki.fi> Date: Tue, 08 Apr 2008 00:00:10 +0300 From: Pekka Enberg User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Hugh Dickins CC: Peter Zijlstra , Christoph Lameter , James Bottomley , Linus Torvalds , Andrew Morton , FUJITA Tomonori , Jens Axboe , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org Subject: Re: [PATCH] scsi: fix sense_slab/bio swapping livelock References: <1207598115.29991.23.camel@lappy> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Hugh, On Mon, 2008-04-07 at 20:40 +0100, Hugh Dickins wrote: > > > If we had a SLAB_NOMERGE flag, would we want to apply it to the > > > bio cache or to the scsi_sense_cache or to both? My difficulty > > > in answering that makes me wonder whether such a flag is right. On Mon, 7 Apr 2008, Peter Zijlstra wrote: > > If this is critical to avoid memory deadlocks, I would suggest using > > mempools (or my reserve framework). Hugh Dickins wrote: > No, the critical part of it has been dealt with (small fix to scsi > free_list handling: which resembles a mempool, but done its own way). > > What remains is about "unsightly" behaviour, the system having a > tendency to collapse briefly into far-from-efficient operation > when out of memory. Although you weren't convinced by my arguments, I still have difficulties understanding why this kind of bad behavior would be acceptable in an embedded environment and why we don't need to fix it for the SLOB case as well. But you do bring up a good point of SLUB changing the behavior on OOM situations for which SLAB_NOMERGE sounds like a good-enough stop-gap measure for the short term. I would prefer some other fix even if it means getting rid of slab merging competely (which would suck as it's very nice for making memory footprint smaller). Pekka