From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [RFC 0/3] virtio: NUMA-aware memory allocation
Date: Tue, 30 Jun 2020 09:47:38 +0100 [thread overview]
Message-ID: <20200630084738.GC81930@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200629112212-mutt-send-email-mst@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1484 bytes --]
On Mon, Jun 29, 2020 at 11:28:41AM -0400, Michael S. Tsirkin wrote:
> On Mon, Jun 29, 2020 at 10:26:46AM +0100, Stefan Hajnoczi wrote:
> > On Sun, Jun 28, 2020 at 02:34:37PM +0800, Jason Wang wrote:
> > >
> > > On 2020/6/25 下午9:57, Stefan Hajnoczi wrote:
> > > > These patches are not ready to be merged because I was unable to measure a
> > > > performance improvement. I'm publishing them so they are archived in case
> > > > someone picks up this work again in the future.
> > > >
> > > > The goal of these patches is to allocate virtqueues and driver state from the
> > > > device's NUMA node for optimal memory access latency. Only guests with a vNUMA
> > > > topology and virtio devices spread across vNUMA nodes benefit from this. In
> > > > other cases the memory placement is fine and we don't need to take NUMA into
> > > > account inside the guest.
> > > >
> > > > These patches could be extended to virtio_net.ko and other devices in the
> > > > future. I only tested virtio_blk.ko.
> > > >
> > > > The benchmark configuration was designed to trigger worst-case NUMA placement:
> > > > * Physical NVMe storage controller on host NUMA node 0
>
> It's possible that numa is not such a big deal for NVMe.
> And it's possible that bios misconfigures ACPI reporting NUMA placement
> incorrectly.
> I think that the best thing to try is to use a ramdisk
> on a specific numa node.
Using ramdisk is an interesting idea, thanks.
Stefan
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2020-06-30 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:57 [RFC 0/3] virtio: NUMA-aware memory allocation Stefan Hajnoczi
2020-06-25 13:57 ` [RFC 1/3] virtio-pci: use NUMA-aware memory allocation in probe Stefan Hajnoczi
2020-06-25 13:57 ` [RFC 2/3] virtio_ring: " Stefan Hajnoczi
2020-06-25 13:57 ` [RFC 3/3] virtio-blk: " Stefan Hajnoczi
2020-06-28 6:34 ` [RFC 0/3] virtio: NUMA-aware memory allocation Jason Wang
2020-06-29 9:26 ` Stefan Hajnoczi
2020-06-29 15:28 ` Michael S. Tsirkin
2020-06-30 8:47 ` Stefan Hajnoczi [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=20200630084738.GC81930@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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