From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
virtualization@lists.linux-foundation.org,
Jason Wang <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH v1 0/4] virtio-mem: memory unplug/offlining related cleanups
Date: Fri, 14 Jul 2023 11:55:28 +0200 [thread overview]
Message-ID: <e609bed0-b6c2-1905-36a8-f94b85fd350b@redhat.com> (raw)
In-Reply-To: <20230713110235-mutt-send-email-mst@kernel.org>
On 13.07.23 17:03, Michael S. Tsirkin wrote:
> On Thu, Jul 13, 2023 at 04:55:47PM +0200, David Hildenbrand wrote:
>> Some cleanups+optimizations primarily around offline_and_remove_memory().
>>
>> Patch #1 drops the "unsafe unplug" feature where we might get stuck in
>> offline_and_remove_memory() forever.
>>
>> Patch #2 handles unexpected errors from offline_and_remove_memory() a bit
>> nicer.
>>
>> Patch #3 handles the case where offline_and_remove_memory() failed and
>> we want to retry later to remove a completely unplugged Linux memory
>> block, to not have them waste memory forever.
>>
>> Patch #4 something I had lying around for longer, which reacts faster
>> on config changes when unplugging memory.
>>
>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
>> Cc: Jason Wang <jasowang@redhat.com>
>> Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>
> This looks like something that's reasonable to put in this linux, right?
> These are fixes even though they are for theoretical issues.
Yes, but these are not high-priority fixes+optimizations. So if you feel
like we should be delaying them, fine with me.
On the other hand, getting them in now also shouldn't really hurt.
Especially patch #1 might be better of just going in soner than later.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2023-07-14 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 14:55 David Hildenbrand
2023-07-13 14:55 ` [PATCH v1 1/4] virtio-mem: remove unsafe unplug in Big Block Mode (BBM) David Hildenbrand
2023-07-13 14:55 ` [PATCH v1 2/4] virtio-mem: convert most offline_and_remove_memory() errors to -EBUSY David Hildenbrand
2023-07-13 14:55 ` [PATCH v1 3/4] virtio-mem: keep retrying on offline_and_remove_memory() errors in Sub Block Mode (SBM) David Hildenbrand
2023-07-13 14:55 ` [PATCH v1 4/4] virtio-mem: check if the config changed before fake offlining memory David Hildenbrand
2023-07-13 15:03 ` [PATCH v1 0/4] virtio-mem: memory unplug/offlining related cleanups Michael S. Tsirkin
2023-07-14 9:55 ` David Hildenbrand [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=e609bed0-b6c2-1905-36a8-f94b85fd350b@redhat.com \
--to=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.com \
/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
all inboxes | Powered by JetHome®