From: Baoquan He <bhe@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
rientjes@google.com, rppt@linux.ibm.com, thomas.lendacky@amd.com,
brijesh.singh@amd.com, kexec@lists.infradead.org,
iommu@lists.linux-foundation.org, m.szyprowski@samsung.com,
robin.murphy@arm.com
Subject: Re: [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool
Date: Thu, 24 Jun 2021 17:29:30 +0800 [thread overview]
Message-ID: <20210624092930.GA802261@MiWiFi-R3L-srv> (raw)
In-Reply-To: <YNQ258KHlzlajqo/@infradead.org>
On 06/24/21 at 08:40am, Christoph Hellwig wrote:
> So reduce the amount allocated. But the pool is needed for proper
> operation on systems with memory encryption. And please add the right
> maintainer or at least mailing list for the code you're touching next
> time.
Oh, I thoutht it's memory issue only, should have run
./scripts/get_maintainer.pl. sorry.
About reducing the amount allocated, it may not help. Because on x86_64,
kdump kernel doesn't put any page of memory into buddy allocator of DMA
zone. Means it will defenitely OOM for atomic_pool_dma initialization.
Wondering in which case or on which device the atomic pool is needed on
AMD system with mem encrytion enabled. As we can see, the OOM will
happen too in kdump kernel on Intel system, even though it's not
necessary.
Thanks
Baoquan
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: thomas.lendacky@amd.com, brijesh.singh@amd.com, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
rppt@linux.ibm.com, linux-mm@kvack.org,
iommu@lists.linux-foundation.org, rientjes@google.com,
robin.murphy@arm.com
Subject: Re: [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool
Date: Thu, 24 Jun 2021 17:29:30 +0800 [thread overview]
Message-ID: <20210624092930.GA802261@MiWiFi-R3L-srv> (raw)
In-Reply-To: <YNQ258KHlzlajqo/@infradead.org>
On 06/24/21 at 08:40am, Christoph Hellwig wrote:
> So reduce the amount allocated. But the pool is needed for proper
> operation on systems with memory encryption. And please add the right
> maintainer or at least mailing list for the code you're touching next
> time.
Oh, I thoutht it's memory issue only, should have run
./scripts/get_maintainer.pl. sorry.
About reducing the amount allocated, it may not help. Because on x86_64,
kdump kernel doesn't put any page of memory into buddy allocator of DMA
zone. Means it will defenitely OOM for atomic_pool_dma initialization.
Wondering in which case or on which device the atomic pool is needed on
AMD system with mem encrytion enabled. As we can see, the OOM will
happen too in kdump kernel on Intel system, even though it's not
necessary.
Thanks
Baoquan
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
rientjes@google.com, rppt@linux.ibm.com, thomas.lendacky@amd.com,
brijesh.singh@amd.com, kexec@lists.infradead.org,
iommu@lists.linux-foundation.org, m.szyprowski@samsung.com,
robin.murphy@arm.com
Subject: Re: [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool
Date: Thu, 24 Jun 2021 17:29:30 +0800 [thread overview]
Message-ID: <20210624092930.GA802261@MiWiFi-R3L-srv> (raw)
In-Reply-To: <YNQ258KHlzlajqo/@infradead.org>
On 06/24/21 at 08:40am, Christoph Hellwig wrote:
> So reduce the amount allocated. But the pool is needed for proper
> operation on systems with memory encryption. And please add the right
> maintainer or at least mailing list for the code you're touching next
> time.
Oh, I thoutht it's memory issue only, should have run
./scripts/get_maintainer.pl. sorry.
About reducing the amount allocated, it may not help. Because on x86_64,
kdump kernel doesn't put any page of memory into buddy allocator of DMA
zone. Means it will defenitely OOM for atomic_pool_dma initialization.
Wondering in which case or on which device the atomic pool is needed on
AMD system with mem encrytion enabled. As we can see, the OOM will
happen too in kdump kernel on Intel system, even though it's not
necessary.
Thanks
Baoquan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2021-06-24 9:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 5:20 [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool Baoquan He
2021-06-24 5:20 ` Baoquan He
2021-06-24 5:20 ` [PATCH 1/2] docs: kernel-parameters: Update to reflect the current default size of " Baoquan He
2021-06-24 5:20 ` Baoquan He
2021-06-24 5:20 ` [PATCH 2/2] dma-pool: allow user to disable " Baoquan He
2021-06-24 5:20 ` Baoquan He
2021-06-24 7:40 ` [PATCH RFC 0/2] " Christoph Hellwig
2021-06-24 7:40 ` Christoph Hellwig
2021-06-24 9:29 ` Baoquan He [this message]
2021-06-24 9:29 ` Baoquan He
2021-06-24 9:29 ` Baoquan He
2021-06-24 10:47 ` Robin Murphy
2021-06-24 10:47 ` Robin Murphy
2021-06-24 10:47 ` Robin Murphy
2021-06-24 12:10 ` Christoph Hellwig
2021-06-24 12:10 ` Christoph Hellwig
2021-06-24 12:10 ` Christoph Hellwig
2021-08-05 6:54 ` Baoquan He
2021-08-05 6:54 ` Baoquan He
2021-08-05 6:54 ` Baoquan He
2021-08-10 20:52 ` Tom Lendacky
2021-08-10 20:52 ` Tom Lendacky
2021-08-10 20:52 ` Tom Lendacky via iommu
2021-08-11 2:23 ` Baoquan He
2021-08-11 2:23 ` Baoquan He
2021-08-11 2:23 ` Baoquan He
2021-08-11 13:46 ` Tom Lendacky
2021-08-11 13:46 ` Tom Lendacky
2021-08-11 13:46 ` Tom Lendacky via iommu
2021-08-11 5:52 ` Christoph Hellwig
2021-08-11 5:52 ` Christoph Hellwig
2021-08-11 5: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=20210624092930.GA802261@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.ibm.com \
--cc=thomas.lendacky@amd.com \
--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 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.