From: Michal Hocko <mhocko@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
linux-mm@kvack.org, cl@linux.com, Jan Kara <jack@suse.cz>,
matthew@wil.cx, x86@kernel.org, luto@amacapital.net,
martin.petersen@oracle.com, jthumshirn@suse.de,
broonie@kernel.org, linux-spi@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [LSF/MM TOPIC NOTES] x86 ZONE_DMA love
Date: Fri, 27 Apr 2018 09:18:43 +0200 [thread overview]
Message-ID: <20180427071843.GB17484@dhcp22.suse.cz> (raw)
In-Reply-To: <20180427053556.GB11339@infradead.org>
On Thu 26-04-18 22:35:56, Christoph Hellwig wrote:
> On Thu, Apr 26, 2018 at 09:54:06PM +0000, Luis R. Rodriguez wrote:
> > In practice if you don't have a floppy device on x86, you don't need ZONE_DMA,
>
> I call BS on that, and you actually explain later why it it BS due
> to some drivers using it more explicitly. But even more importantly
> we have plenty driver using it through dma_alloc_* and a small DMA
> mask, and they are in use - we actually had a 4.16 regression due to
> them.
Well, but do we need a zone for that purpose? The idea was to actually
replace the zone by a CMA pool (at least on x86). With the current
implementation of the CMA we would move the range [0-16M] pfn range into
zone_movable so it can be used and we would get rid of all of the
overhead each zone brings (a bit in page flags, kmalloc caches and who
knows what else)
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-27 7:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 21:54 [LSF/MM TOPIC NOTES] x86 ZONE_DMA love Luis R. Rodriguez
2018-04-27 1:09 ` [Lsf-pc] " Rik van Riel
2018-04-27 5:35 ` Christoph Hellwig
2018-04-27 7:18 ` Michal Hocko [this message]
2018-04-27 16:07 ` Christopher Lameter
2018-04-27 16:18 ` Matthew Wilcox
2018-04-27 16:36 ` Christopher Lameter
2018-04-28 8:33 ` Christoph Hellwig
2018-04-27 16:37 ` Michal Hocko
2018-04-28 8:33 ` Christoph Hellwig
2018-04-28 8:30 ` Christoph Hellwig
2018-04-27 16:14 ` Luis R. Rodriguez
2018-04-27 16:28 ` Matthew Wilcox
2018-04-28 8:42 ` Christoph Hellwig
2018-04-28 18:55 ` Luis R. Rodriguez
2018-04-28 19:46 ` Julia Lawall
2018-04-28 20:41 ` Matthew Wilcox
2018-04-29 14:34 ` Julia Lawall
[not found] ` <CAFhKne8u7KcBkpgiQ0fFZyh5_EorfY-_MJJaEYk3feCOd9LsRQ@mail.gmail.com>
2018-05-03 12:03 ` Michal Hocko
2018-05-03 12:13 ` Christoph Hellwig
2018-05-03 8:20 ` Geert Uytterhoeven
2018-05-05 16:08 ` Are media drivers abusing of GFP_DMA? - was: " Mauro Carvalho Chehab
2018-05-07 13:26 ` Laurent Pinchart
2018-05-07 15:19 ` Mauro Carvalho Chehab
2018-05-14 8:00 ` Fabien DESSENNE
2018-05-14 10:35 ` Mauro Carvalho Chehab
2018-05-14 10:39 ` Mauro Carvalho Chehab
2018-05-15 7:30 ` Fabien DESSENNE
2018-05-15 8:27 ` Laurent Pinchart
2018-05-15 10:30 ` Mauro Carvalho Chehab
2018-05-15 16:24 ` Luis R. Rodriguez
2018-05-10 4:39 ` Yasunari.Takiguchi
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=20180427071843.GB17484@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=broonie@kernel.org \
--cc=cl@linux.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=luto@amacapital.net \
--cc=martin.petersen@oracle.com \
--cc=matthew@wil.cx \
--cc=mcgrof@kernel.org \
--cc=x86@kernel.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 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).