From: Christoph Hellwig <hch@lst.de>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, hch@lst.de, robin.murphy@arm.com,
cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, m.szyprowski@samsung.com,
John.p.donnelly@oracle.com, kexec@lists.infradead.org
Subject: Re: [PATCH RESEND v2 2/5] dma-pool: allow user to disable atomic pool
Date: Mon, 13 Dec 2021 08:44:04 +0100 [thread overview]
Message-ID: <20211213074404.GA20758@lst.de> (raw)
In-Reply-To: <20211207030750.30824-3-bhe@redhat.com>
On Tue, Dec 07, 2021 at 11:07:47AM +0800, Baoquan He wrote:
> In the current code, three atomic memory pools are always created,
> atomic_pool_kernel|dma|dma32, even though 'coherent_pool=0' is
> specified in kernel command line. In fact, atomic pool is only
> necessary when CONFIG_DMA_DIRECT_REMAP=y or mem_encrypt_active=y
> which are needed on few ARCHes.
And only these select the atomic pool, so it won't get created otherwise.
What problem are you trying to solve?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, hch@lst.de, robin.murphy@arm.com,
cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, m.szyprowski@samsung.com,
John.p.donnelly@oracle.com, kexec@lists.infradead.org
Subject: Re: [PATCH RESEND v2 2/5] dma-pool: allow user to disable atomic pool
Date: Mon, 13 Dec 2021 08:44:04 +0100 [thread overview]
Message-ID: <20211213074404.GA20758@lst.de> (raw)
In-Reply-To: <20211207030750.30824-3-bhe@redhat.com>
On Tue, Dec 07, 2021 at 11:07:47AM +0800, Baoquan He wrote:
> In the current code, three atomic memory pools are always created,
> atomic_pool_kernel|dma|dma32, even though 'coherent_pool=0' is
> specified in kernel command line. In fact, atomic pool is only
> necessary when CONFIG_DMA_DIRECT_REMAP=y or mem_encrypt_active=y
> which are needed on few ARCHes.
And only these select the atomic pool, so it won't get created otherwise.
What problem are you trying to solve?
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2021-12-13 7:44 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 3:07 [PATCH RESEND v2 0/5] Avoid requesting page from DMA zone when no managed pages Baoquan He
2021-12-07 3:07 ` Baoquan He
2021-12-07 3:07 ` [PATCH RESEND v2 1/5] docs: kernel-parameters: Update to reflect the current default size of atomic pool Baoquan He
2021-12-07 3:07 ` Baoquan He
2021-12-07 3:53 ` John Donnelly
2021-12-07 3:53 ` John Donnelly
2021-12-07 3:07 ` [PATCH RESEND v2 2/5] dma-pool: allow user to disable " Baoquan He
2021-12-07 3:07 ` Baoquan He
2021-12-07 3:53 ` John Donnelly
2021-12-07 3:53 ` John Donnelly
2021-12-13 7:44 ` Christoph Hellwig [this message]
2021-12-13 7:44 ` Christoph Hellwig
2021-12-13 8:16 ` Baoquan He
2021-12-13 8:16 ` Baoquan He
2021-12-07 3:07 ` [PATCH RESEND v2 3/5] mm_zone: add function to check if managed dma zone exists Baoquan He
2021-12-07 3:07 ` Baoquan He
2021-12-07 3:53 ` John Donnelly
2021-12-07 3:53 ` John Donnelly
2021-12-07 11:23 ` David Hildenbrand
2021-12-07 11:23 ` David Hildenbrand
2021-12-09 13:02 ` Baoquan He
2021-12-09 13:02 ` Baoquan He
2021-12-09 13:10 ` David Hildenbrand
2021-12-09 13:10 ` David Hildenbrand
2021-12-09 13:23 ` Baoquan He
2021-12-09 13:23 ` Baoquan He
2021-12-07 3:07 ` [PATCH RESEND v2 4/5] dma/pool: create dma atomic pool only if dma zone has managed pages Baoquan He
2021-12-07 3:07 ` Baoquan He
2021-12-07 3:07 ` Baoquan He
2021-12-07 3:54 ` John Donnelly
2021-12-07 3:54 ` John Donnelly
2021-12-07 3:54 ` John Donnelly
2021-12-07 3:07 ` [PATCH RESEND v2 5/5] mm/slub: do not create dma-kmalloc if no managed pages in DMA zone Baoquan He
2021-12-07 3:07 ` Baoquan He
2021-12-07 3:54 ` John Donnelly
2021-12-07 3:54 ` John Donnelly
2021-12-07 3:16 ` [PATCH RESEND v2 0/5] Avoid requesting page from DMA zone when no managed pages Baoquan He
2021-12-07 3:16 ` Baoquan He
2021-12-07 4:03 ` John Donnelly
2021-12-07 4:03 ` John Donnelly
2021-12-08 4:33 ` Andrew Morton
2021-12-08 4:33 ` Andrew Morton
2021-12-08 4:56 ` John Donnelly
2021-12-08 4:56 ` John Donnelly
2021-12-13 3:54 ` Baoquan He
2021-12-13 3:54 ` Baoquan He
2021-12-13 13:25 ` Borislav Petkov
2021-12-13 13:25 ` Borislav Petkov
2021-12-13 14:03 ` Baoquan He
2021-12-13 14:03 ` Baoquan He
2021-12-07 8:05 ` Christoph Lameter
2021-12-07 8:05 ` Christoph Lameter
2021-12-09 8:05 ` Baoquan He
2021-12-09 8:05 ` Baoquan He
2021-12-09 12:59 ` Christoph Lameter
2021-12-09 12:59 ` Christoph Lameter
2021-12-13 7:39 ` Baoquan He
2021-12-13 7:39 ` Baoquan He
2021-12-13 7:49 ` Christoph Hellwig
2021-12-13 7:49 ` Christoph Hellwig
2021-12-13 14:21 ` Hyeonggon Yoo
2021-12-13 14:21 ` Hyeonggon Yoo
2021-12-13 7:47 ` Christoph Hellwig
2021-12-13 7:47 ` 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=20211213074404.GA20758@lst.de \
--to=hch@lst.de \
--cc=John.p.donnelly@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--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 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.