Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262585AbUJ0RoD (ORCPT ); Wed, 27 Oct 2004 13:44:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262579AbUJ0RoB (ORCPT ); Wed, 27 Oct 2004 13:44:01 -0400 Received: from e5.ny.us.ibm.com ([32.97.182.105]:59279 "EHLO e5.ny.us.ibm.com") by vger.kernel.org with ESMTP id S262591AbUJ0Rhm (ORCPT ); Wed, 27 Oct 2004 13:37:42 -0400 Date: Wed, 27 Oct 2004 10:36:48 -0700 From: "Martin J. Bligh" To: Jeff Garzik cc: Linux Kernel , linux-mm@kvack.org, Bartlomiej Zolnierkiewicz , "Randy.Dunlap" , William Lee Irwin III , Jens Axboe , Andrew Morton Subject: Re: news about IDE PIO HIGHMEM bug (was: Re: 2.6.9-mm1) Message-ID: <30640000.1098898608@flay> In-Reply-To: <417FC5CB.9040204@pobox.com> References: <58cb370e041027074676750027@mail.gmail.com> <417FBB6D.90401@pobox.com> <1246230000.1098892359@[10.10.2.4]> <417FC5CB.9040204@pobox.com> X-Mailer: Mulberry/2.1.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 19 > Unfortunately, it's not. > > The block layer just tells us "it's a contiguous run of memory", which implies nothing really about the allocation size. > > Bart and I (and others?) essentially need a "page+1" thing (for 2.4.x too!), that won't break in the face of NUMA/etc. > > Alternatively (or additionally), we may need to make sure the block layer doesn't merge across zones or NUMA boundaries or whatnot. The latter would be rather more efficient. I don't know how often you end up doing each operation though ... the page+1 vs the attemtped merge. Depends on the ratio, I guess. M. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/