From: hch@infradead.org (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mm: cma: honor __GFP_ZERO flag in cma_alloc()
Date: Mon, 2 Jul 2018 06:30:16 -0700 [thread overview]
Message-ID: <20180702133016.GA16909@infradead.org> (raw)
In-Reply-To: <20180702132335eucas1p1323fbf51cd5e82a59939d72097acee04~9kAizDyji0466904669eucas1p1w@eucas1p1.samsung.com>
On Mon, Jul 02, 2018 at 03:23:34PM +0200, Marek Szyprowski wrote:
> What about clearing the allocated buffer? Should it be another bool
> parameter,
> done unconditionally or moved to the callers?
Please keep it in the callers. I plan to push it up even higher
from the current callers short to midterm.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>,
Michal Nazarewicz <mina86@mina86.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm: cma: honor __GFP_ZERO flag in cma_alloc()
Date: Mon, 2 Jul 2018 06:30:16 -0700 [thread overview]
Message-ID: <20180702133016.GA16909@infradead.org> (raw)
In-Reply-To: <20180702132335eucas1p1323fbf51cd5e82a59939d72097acee04~9kAizDyji0466904669eucas1p1w@eucas1p1.samsung.com>
On Mon, Jul 02, 2018 at 03:23:34PM +0200, Marek Szyprowski wrote:
> What about clearing the allocated buffer? Should it be another bool
> parameter,
> done unconditionally or moved to the callers?
Please keep it in the callers. I plan to push it up even higher
from the current callers short to midterm.
next prev parent reply other threads:[~2018-07-02 13:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180613085851eucas1p20337d050face8ff8ea87674e16a9ccd2@eucas1p2.samsung.com>
2018-06-13 8:58 ` [PATCH] mm: cma: honor __GFP_ZERO flag in cma_alloc() Marek Szyprowski
2018-06-13 8:58 ` Marek Szyprowski
2018-06-13 12:24 ` Matthew Wilcox
2018-06-13 12:24 ` Matthew Wilcox
2018-06-13 12:40 ` Marek Szyprowski
2018-06-13 12:40 ` Marek Szyprowski
2018-06-13 12:55 ` Christoph Hellwig
2018-06-13 12:55 ` Christoph Hellwig
2018-06-13 13:39 ` Michal Hocko
2018-06-13 13:39 ` Michal Hocko
2018-07-02 13:23 ` Marek Szyprowski
2018-07-02 13:23 ` Marek Szyprowski
2018-07-02 13:30 ` Christoph Hellwig [this message]
2018-07-02 13:30 ` Christoph Hellwig
2018-07-09 10:32 ` Marek Szyprowski
2018-07-09 10:32 ` Marek Szyprowski
2018-07-02 13:32 ` Michal Hocko
2018-07-02 13:32 ` Michal Hocko
2018-07-09 10:31 ` Marek Szyprowski
2018-07-09 10:31 ` Marek Szyprowski
2018-06-13 12:52 ` Christoph Hellwig
2018-06-13 12:52 ` Christoph Hellwig
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=20180702133016.GA16909@infradead.org \
--to=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.