From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754819AbZBRAsZ (ORCPT ); Tue, 17 Feb 2009 19:48:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751759AbZBRAsQ (ORCPT ); Tue, 17 Feb 2009 19:48:16 -0500 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:56603 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751723AbZBRAsP (ORCPT ); Tue, 17 Feb 2009 19:48:15 -0500 From: KOSAKI Motohiro To: Christoph Lameter Subject: Re: [patch] SLQB slab allocator (try 2) Cc: kosaki.motohiro@jp.fujitsu.com, Pekka Enberg , Johannes Weiner , Mel Gorman , Nick Piggin , Nick Piggin , Linux Memory Management List , Linux Kernel Mailing List , Andrew Morton , Lin Ming , "Zhang, Yanmin" In-Reply-To: References: <84144f020902171143i5844ef83h20cb4bee4f65c904@mail.gmail.com> Message-Id: <20090218093858.8990.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.50 [ja] Date: Wed, 18 Feb 2009 09:48:09 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Tue, 17 Feb 2009, Pekka Enberg wrote: > > > >> +#define SLUB_MAX_SIZE (2 * PAGE_SIZE) > > > > On Tue, Feb 17, 2009 at 8:11 PM, Johannes Weiner wrote: > > > This relies on PAGE_SIZE being 4k. If you want 8k, why don't you say > > > so? Pekka did this explicitely. > > > > That could be a problem, sure. Especially for architecture that have 64 K pages. > > You could likely put a complicated formula in there instead. But 2 * > PAGE_SIZE is simple and will work on all platforms regardless of pagesize. I think 2 * PAGE_SIZE is best and the patch description is needed change. it's because almost architecture use two pages for stack and current page allocator don't have delayed consolidation mechanism for order-1 page. In addition, if pekka patch (SLAB_LIMIT = 8K) run on ia64, 16K allocation always fallback to page allocator and using 64K (4 times memory consumption!). Am I misunderstand anything?