From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f197.google.com (mail-wr0-f197.google.com [209.85.128.197]) by kanga.kvack.org (Postfix) with ESMTP id E03DD6B036C for ; Wed, 16 May 2018 17:21:50 -0400 (EDT) Received: by mail-wr0-f197.google.com with SMTP id f23-v6so1565753wra.20 for ; Wed, 16 May 2018 14:21:50 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id 189-v6sor931779wmu.47.2018.05.16.14.21.48 for (Google Transport Security); Wed, 16 May 2018 14:21:49 -0700 (PDT) MIME-Version: 1.0 References: <20180516202023.167627-1-shakeelb@google.com> <90167afa-ecfb-c5ef-3554-ddb7e6ac9728@suse.cz> In-Reply-To: <90167afa-ecfb-c5ef-3554-ddb7e6ac9728@suse.cz> From: Shakeel Butt Date: Wed, 16 May 2018 14:21:35 -0700 Message-ID: Subject: Re: [PATCH] mm: save two stranding bit in gfp_mask Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Vlastimil Babka Cc: Michal Hocko , Andrew Morton , Greg Thelen , Mel Gorman , Linux MM , LKML On Wed, May 16, 2018 at 1:41 PM Vlastimil Babka wrote: > On 05/16/2018 10:20 PM, Shakeel Butt wrote: > > ___GFP_COLD and ___GFP_OTHER_NODE were removed but their bits were > > stranded. Slide existing gfp masks to make those two bits available. > Well, there are already available for hypothetical new flags. Is there > anything that benefits from a smaller __GFP_BITS_SHIFT? I am prototyping to pass along the type of kmem allocation e.g. page table, vmalloc, stack e.t.c. (still very preliminary).