Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp470203yba; Fri, 5 Apr 2019 10:12:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqyOKqlkxmYEb1KQw1gItJ47m0Px0WpVjoM8ni00Z38PhNo4Dl5rdD6QeIujckXrbZ/R4XHS X-Received: by 2002:a63:df12:: with SMTP id u18mr13326521pgg.135.1554484334302; Fri, 05 Apr 2019 10:12:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554484334; cv=none; d=google.com; s=arc-20160816; b=Mb3KSqt1eEXJMQXumdjMRyzPjDNHBx1B5HhkmnQHyRlEgfyi8tU7HOQcpyBVm/dBVi bXqtg/QLiRZF/vkO5K9WqXN3qLvpWJHZlnNS4e+uALUFEJs2StGVRbXlR91oszeOuE7T BJqtrze4YjLxfTplV1MNYsoSFZmonKgaP3QAWSGt62nS4O2r+u3fMf808PbzePZFrhcv ACe/t5CdlSYP6NwOwIpt/eXiES59WgSHJVuk8DzUFnivUR5ATXBa9M7ZJxX37JTm+zPw IuQ+KDIZPyR+rMY+eMkHvDduvM+IFBSTVJbZ8PxaJFSsMC9hL5tFUGuSAjv23CdGPnaE LXaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=jWxk0GETdbMHBeJfcbGAniuJenh+xldWuNdVk5rPuLc=; b=Xcq0gP/y+D3f3CKjdmRb4et9b6cMIJJdo06Nxub+pw1kZFhIzJ7cuKULhESYvutTSq CDeo/VDQCdPsNFbH+BIEcChmawYgVST1vHnbqJb05p+2JPWXYhnHzThR8jDprWxyWkj4 uLH6/iNtvlskQkqrfpBRetaIK6+u/yfxa+5pb2FpRTkPi/DZJ6Ot5hQoFvIu3odyzPxW TsLoY+9TEBPe9YyE91JculFIy0WOM84BXGu6M37r8Cf4al1wtdJEI6kgWHlbNAerdUmg eoOoLFQAibRfoHhy1AokzenLgt7P88L154JNi7a6HxDXUhxh1MVabbNUVHka+AKqyEHz ssLg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f128si19008748pgc.473.2019.04.05.10.11.57; Fri, 05 Apr 2019 10:12:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731474AbfDERLV (ORCPT + 99 others); Fri, 5 Apr 2019 13:11:21 -0400 Received: from mx2.suse.de ([195.135.220.15]:55520 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730870AbfDERLV (ORCPT ); Fri, 5 Apr 2019 13:11:21 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 4FCB0AD7C; Fri, 5 Apr 2019 17:11:19 +0000 (UTC) Subject: Re: [RFC 0/2] guarantee natural alignment for kmalloc() To: Christopher Lameter Cc: linux-mm@kvack.org, Pekka Enberg , David Rientjes , Joonsoo Kim , Ming Lei , Dave Chinner , Matthew Wilcox , "Darrick J . Wong" , Christoph Hellwig , Michal Hocko , linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org References: <20190319211108.15495-1-vbabka@suse.cz> <01000169988d4e34-b4178f68-c390-472b-b62f-a57a4f459a76-000000@email.amazonses.com> <5d7fee9c-1a80-6ac9-ac1d-b1ce05ed27a8@suse.cz> <010001699c5563f8-36c6909f-ed43-4839-82da-b5f9f21594b8-000000@email.amazonses.com> <4d2a55dc-b29f-1309-0a8e-83b057e186e6@suse.cz> <01000169a68852ed-d621a35c-af0c-4759-a8a3-e97e7dfc17a5-000000@email.amazonses.com> From: Vlastimil Babka Message-ID: <2b129aec-f9a5-7ab8-ca4a-0a325621d111@suse.cz> Date: Fri, 5 Apr 2019 19:11:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <01000169a68852ed-d621a35c-af0c-4759-a8a3-e97e7dfc17a5-000000@email.amazonses.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/22/19 6:52 PM, Christopher Lameter wrote: > On Thu, 21 Mar 2019, Vlastimil Babka wrote: > >> That however doesn't work well for the xfs/IO case where block sizes are >> not known in advance: >> >> https://lore.kernel.org/linux-fsdevel/20190225040904.5557-1-ming.lei@redhat.com/T/#ec3a292c358d05a6b29cc4a9ce3ae6b2faf31a23f > > I thought we agreed to use custom slab caches for that? Hm maybe I missed something but my impression was that xfs/IO folks would have to create lots of them for various sizes not known in advance, and that it wasn't practical and would welcome if kmalloc just guaranteed the alignment. But so far they haven't chimed in here in this thread, so I guess I'm wrong.