From: Dev Audsin <dev.devaqemu@gmail.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, qemu-trivial@nongnu.org,
dgilber@redhat.com, dev.devaqemu@gmail.com
Subject:
Date: Mon, 26 Apr 2021 13:05:52 -0700 [thread overview]
Message-ID: <20210426200553.145976-1-dev.devaqemu@gmail.com> (raw)
virtio-fs with DAX is currently not compatible with NIC Pass through.
When a SR-IOV VF attaches to a qemu process, vfio will try to pin the entire DAX Window but it is empty when the guest boots and will fail.
A method to make VFIO and DAX to work together is to make vfio skip DAX cache.
Currently DAX cache need to be set to 0, for the SR-IOV VF to be attached to Kata containers.
Enabling both SR-IOV VF and DAX work together will potentially improve performance for workloads which are I/O and network intensive
WARNING: multiple messages have this Message-ID (diff)
From: Dev Audsin <dev.devaqemu@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, alex.williamson@redhat.com,
dgilber@redhat.com, dev.devaqemu@gmail.com
Subject:
Date: Mon, 26 Apr 2021 13:05:52 -0700 [thread overview]
Message-ID: <20210426200553.145976-1-dev.devaqemu@gmail.com> (raw)
virtio-fs with DAX is currently not compatible with NIC Pass through.
When a SR-IOV VF attaches to a qemu process, vfio will try to pin the entire DAX Window but it is empty when the guest boots and will fail.
A method to make VFIO and DAX to work together is to make vfio skip DAX cache.
Currently DAX cache need to be set to 0, for the SR-IOV VF to be attached to Kata containers.
Enabling both SR-IOV VF and DAX work together will potentially improve performance for workloads which are I/O and network intensive
next reply other threads:[~2021-04-27 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 20:05 Dev Audsin [this message]
2021-04-26 20:05 ` Dev Audsin
2021-04-26 20:05 ` [PATCH] skip virtio fs cache section to enable NIC passthrough Dev Audsin
2021-04-26 20:05 ` Dev Audsin
2021-04-27 0:27 ` no-reply
2021-04-27 0:27 ` no-reply
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=20210426200553.145976-1-dev.devaqemu@gmail.com \
--to=dev.devaqemu@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=dgilber@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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.