Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3677054yba; Tue, 9 Apr 2019 02:21:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqyHXzgTZ7ZUwGwWkTQRnrVBqCbCdeBx+3G45kUTmH406qy+faGN143SmuSesqT/w9mKjWiT X-Received: by 2002:a62:19c3:: with SMTP id 186mr36092356pfz.172.1554801715887; Tue, 09 Apr 2019 02:21:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554801715; cv=none; d=google.com; s=arc-20160816; b=E3/+bVOfILz6ljsAzfxbVnN/Y5R5xP8joPxRyXI2Jwytx7RQPzxQtVJuIfV7Xeva6K SJQ8O8fJB+VATtbJA8p8H2GUvW4G2Nd1Y02SE7yF0jXQP/yDSB3Uew9VtXioHjSffcqU nG/cfTSrZ4ffAtEaPFqklSOyi2uIXs8L+r07bAWqdd6sMWYt2V0gzxsCrVD9zRrh4xAr FHy3uT5OA8zBnVzWjCYPdPCRi8E73YRbFCt0yK6lUC9fy7iDPd5dLJKQivwlxe6/l+no Y8zEHQyxZQXb1bUhHjjO3j2zPZwoGV+/kKhDs7Qasxp6mo+1BVR6aAMgoWKmK4A3Ce5L +v4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=LWYtPi/oAp5kLr9CpcOmqDnw+cN50JJ0w+QimGsCwAQ=; b=OVvQljEZhbyLV1eTiaOLNLYzXZ43EIdFpwDrU7RTKysC3Bjs9KnyLxrWZCILi0bLQs WArHDEzGuBvG4bt8JpxWyjS/fvJhnRVSX7cn7Z6AFtVo9Mv9kTvL8EVPjoQO6xXBYtu0 myLRJ9yUTFGqCtS0LGA2BDLSpHe/Jt5OQHVqBqnx8R05jU/rt9jskcLIU7xZpCvWLhkv OPnppOR6gfrXpoUCllLdqFQgpOhMIfNa/JCBlMqyIKSdxPUwQgID2lIdLWc/FD9xiUA4 cQWPxBeLZJ7pxcI48y0ZCBy54KrLpJNdlttfPWYiPTkUnTMSli954wCv7yD3aXyIcK1C 6mnQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 129si31614125pfz.159.2019.04.09.02.21.40; Tue, 09 Apr 2019 02:21:55 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726862AbfDIJUr (ORCPT + 99 others); Tue, 9 Apr 2019 05:20:47 -0400 Received: from mx2.suse.de ([195.135.220.15]:38886 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726530AbfDIJUq (ORCPT ); Tue, 9 Apr 2019 05:20:46 -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 8F75FAEDF; Tue, 9 Apr 2019 09:20:44 +0000 (UTC) Date: Tue, 9 Apr 2019 11:20:42 +0200 From: Michal Hocko To: Vlastimil Babka Cc: Christoph Hellwig , Christopher Lameter , linux-mm@kvack.org, Pekka Enberg , David Rientjes , Joonsoo Kim , Ming Lei , Dave Chinner , Matthew Wilcox , "Darrick J . Wong" , linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org, lsf-pc@lists.linux-foundation.org Subject: Re: [RFC 0/2] guarantee natural alignment for kmalloc() Message-ID: <20190409092042.GB10383@dhcp22.suse.cz> 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> <2b129aec-f9a5-7ab8-ca4a-0a325621d111@suse.cz> <20190407080020.GA9949@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 09-04-19 10:07:42, Vlastimil Babka wrote: > On 4/7/19 10:00 AM, Christoph Hellwig wrote: > > On Fri, Apr 05, 2019 at 07:11:17PM +0200, Vlastimil Babka wrote: > >> 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. > > > > Yes, in XFS we might have quite a few. Never mind all the other > > block level consumers that might have similar reasonable expectations > > but haven't triggered the problematic drivers yet. > > What about a LSF session/BoF to sort this out, then? Would need to have people > from all three MM+FS+IO groups, I suppose. Sounds like a good plan. Care to send an email to lsf-pc mailing list so that it doesn't fall through cracks please? -- Michal Hocko SUSE Labs