From: Christoph Hellwig <hch@lst.de>
To: john.p.donnelly@oracle.com
Cc: Christoph Hellwig <hch@lst.de>, Baoquan He <bhe@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, cl@linux.com,
kexec@lists.infradead.org, stable@vger.kernel.org,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v3 5/5] mm/slub: do not create dma-kmalloc if no managed pages in DMA zone
Date: Wed, 15 Dec 2021 08:27:44 +0100 [thread overview]
Message-ID: <20211215072744.GB3010@lst.de> (raw)
In-Reply-To: <dc648afe-6dbe-55c9-ebf6-9334d71706b4@oracle.com>
On Tue, Dec 14, 2021 at 11:07:34AM -0600, john.p.donnelly@oracle.com wrote:
> Is CONFIG_ZONE_DMA even needed anymore in x86_64 ?
Yes. There are still plenty of addressing challenged devices, mostly
ISA-like but also a few PCI/PCIe ones.
prev parent reply other threads:[~2021-12-15 7:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211213122712.23805-1-bhe@redhat.com>
2021-12-13 12:27 ` [PATCH v3 3/5] mm_zone: add function to check if managed dma zone exists Baoquan He
2021-12-13 14:22 ` john.p.donnelly
2021-12-16 10:52 ` David Hildenbrand
2021-12-13 12:27 ` [PATCH v3 4/5] dma/pool: create dma atomic pool only if dma zone has managed pages Baoquan He
2021-12-13 14:23 ` john.p.donnelly
2021-12-13 12:27 ` [PATCH v3 5/5] mm/slub: do not create dma-kmalloc if no managed pages in DMA zone Baoquan He
2021-12-13 13:43 ` Hyeonggon Yoo
2021-12-14 5:32 ` Baoquan He
2021-12-14 10:09 ` Vlastimil Babka
2021-12-14 10:28 ` Christoph Lameter
2021-12-15 4:48 ` Hyeonggon Yoo
2021-12-15 7:03 ` Hyeonggon Yoo
2021-12-15 7:27 ` Christoph Hellwig
2021-12-15 10:34 ` Vlastimil Babka
2021-12-15 11:51 ` David Laight
2021-12-15 13:41 ` Baoquan He
2021-12-17 11:38 ` Hyeonggon Yoo
2021-12-20 7:32 ` Baoquan He
2022-01-07 11:56 ` Hyeonggon Yoo
2021-12-15 14:42 ` Baoquan He
2021-12-15 10:08 ` Baoquan He
2021-12-17 11:38 ` Hyeonggon Yoo
2021-12-21 8:56 ` Christoph Hellwig
2021-12-22 12:37 ` Hyeonggon Yoo
2021-12-23 8:52 ` Christoph Hellwig
2021-12-13 14:24 ` john.p.donnelly
2021-12-14 16:31 ` Christoph Hellwig
2021-12-14 17:07 ` john.p.donnelly
2021-12-15 7:27 ` Christoph Hellwig [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=20211215072744.GB3010@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.p.donnelly@oracle.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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).