From: Vlastimil Babka <vbabka@suse.cz>
To: David Laight <David.Laight@ACULAB.COM>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 'Bart Van Assche' <bvanassche@acm.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Christoph Lameter <cl@linux.com>, Roman Gushchin <guro@fb.com>,
"Darryl T. Agostinelli" <dagostinelli@gmail.com>,
linux-mm <linux-mm@kvack.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] slab.h: Avoid using & for logical and of booleans
Date: Wed, 21 Nov 2018 14:22:49 +0100 [thread overview]
Message-ID: <80340595-d7c5-97b9-4f6c-23fa893a91e9@suse.cz> (raw)
In-Reply-To: <aa5975b6-58ed-5a3e-7de1-4b1384f88457@suse.cz>
On 11/13/18 7:22 PM, Vlastimil Babka wrote:
> On 11/12/18 10:55 AM, David Laight wrote:
>> From: Vlastimil Babka [mailto:vbabka@suse.cz]
>>> Sent: 09 November 2018 19:16
>> ...
>>> This? Not terribly elegant, but I don't see a nicer way right now...
>>
>> Maybe just have two copies of the function body?
>>
>> static __always_inline enum kmalloc_cache_type kmalloc_type(gfp_t flags)
>> {
>> #ifndef CONFIG_ZONE_DMA
>> return flags & __GFP_RECLAIMABLE ? KMALLOC_RECLAIM : KMALLOC_NORMAL;
>> #else
>> if (likely((flags & (__GFP_DMA | __GFP_RECLAIMABLE)) == 0))
>> return KMALLOC_NORMAL;
>> return flags & __GFP_DMA ? KMALLOC_DMA : KMALLOC_RECLAIM;
>> #endif
>> }
>
> OK that's probably the most straightforward to follow, thanks.
> Note that for CONFIG_ZONE_DMA=n the result is identical to original code and
> all other attempts. flags & __GFP_DMA is converted to 1/0 index without branches
> or cmovs or whatnot.
Ping? Seems like people will report duplicates until the sparse warning
is gone in mainline...
Also CC linux-mm which was somehow lost.
----8<----
prev parent reply other threads:[~2018-11-21 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181105204000.129023-1-bvanassche@acm.org>
2018-11-05 21:13 ` [PATCH] slab.h: Avoid using & for logical and of booleans Andrew Morton
2018-11-05 21:48 ` Bart Van Assche
2018-11-05 22:14 ` Rasmus Villemoes
2018-11-05 22:40 ` Bart Van Assche
2018-11-05 22:48 ` Alexander Duyck
2018-11-06 0:01 ` Bart Van Assche
2018-11-06 0:11 ` Alexander Duyck
2018-11-06 0:32 ` Bart Van Assche
2018-11-06 17:20 ` Alexander Duyck
2018-11-06 17:48 ` Bart Van Assche
2018-11-06 18:17 ` Alexander Duyck
2018-11-06 9:45 ` William Kucharski
[not found] ` <62188a351f2249188ce654ee03c894b1@AcuMS.aculab.com>
[not found] ` <e44e6c8b-e4e4-e7cb-a5ca-88e9559eb0d7@suse.cz>
[not found] ` <3c9adab0f1f74c46a60b3d4401030337@AcuMS.aculab.com>
[not found] ` <60deb90d-e521-39e5-5072-fc9efb98e365@suse.cz>
[not found] ` <9af3ac1d43bb422cb3c41e7e8e422e6e@AcuMS.aculab.com>
[not found] ` <cbc1fc52-dc8c-aa38-8f29-22da8bcd91c1@suse.cz>
[not found] ` <20181109110019.c82fba8125d4e2891fbe4a6c@linux-foundation.org>
[not found] ` <b8ffd59b-0d15-9c98-b9ea-ad71e4c0c734@suse.cz>
[not found] ` <bf7c2a6b801a4430bf842fc20e826db6@AcuMS.aculab.com>
[not found] ` <aa5975b6-58ed-5a3e-7de1-4b1384f88457@suse.cz>
2018-11-21 13:22 ` Vlastimil Babka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80340595-d7c5-97b9-4f6c-23fa893a91e9@suse.cz \
--to=vbabka@suse.cz \
--cc=David.Laight@ACULAB.COM \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=cl@linux.com \
--cc=dagostinelli@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).