From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eugenio Perez Martin <eperezma@redhat.com>
Cc: Rob Miller <rob.miller@broadcom.com>,
Virtio-Dev <virtio-dev@lists.oasis-open.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [virtio-dev] Dirty Page Tracking (DPT)
Date: Thu, 9 Apr 2020 17:06:38 -0400 [thread overview]
Message-ID: <20200409170152-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJaqyWfeSgj=+RMM_Zy4gTAkNJ42Ax5Axvc8okHOhH7UTsxhaA@mail.gmail.com>
On Tue, Apr 07, 2020 at 11:52:46AM +0200, Eugenio Perez Martin wrote:
> Hi!
>
> So, from the previous mails, it seems that monitoring the used ring
> (and the packed descriptors) is a good first step in that direction,
> as DPDK did. This way, the device does not need to worry about the
> dirty page tracking using a bitmap and the PCI writes limitation, and
> we can evaluate later the proposed alternatives:
> * Alternate used descriptors in packed.
> * vDPA interface for vDPA devices in a convenient format.
>
> Any thoughts? Do you think that we should start with another way?
>
> Thanks!
I am concerned that with software in data path, we'll hit RX queue
underruns, won't we?
Two ways to avoid underruns:
- dirty page tracking
- page faults
I'm working on a proposal for page faults now. If someone wants
to work on dirty tracking in addition, that's also an option.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2020-04-09 21:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 15:40 [virtio-dev] Dirty Page Tracking (DPT) Rob Miller
2020-03-09 7:38 ` Michael S. Tsirkin
2020-03-09 8:50 ` Jason Wang
2020-03-09 10:13 ` Michael S. Tsirkin
2020-03-10 3:22 ` Jason Wang
2020-03-10 6:24 ` Michael S. Tsirkin
2020-03-10 6:39 ` Jason Wang
2020-03-18 15:13 ` Rob Miller
2020-03-19 3:35 ` Jason Wang
2020-03-19 11:17 ` Paolo Bonzini
2020-04-07 9:52 ` Eugenio Perez Martin
2020-04-07 10:27 ` Rob Miller
2020-04-07 16:31 ` Eugenio Perez Martin
2020-04-08 10:10 ` Jason Wang
2020-04-07 10:40 ` Rob Miller
2020-04-08 10:00 ` Jason Wang
2020-04-09 21:06 ` Michael S. Tsirkin [this message]
2020-04-10 2:40 ` Jason Wang
2020-04-13 12:15 ` Eugenio Perez Martin
2020-04-13 13:30 ` Rob Miller
2020-04-13 13:49 ` Jason Wang
2020-04-13 13:49 ` Jason Wang
2020-04-13 13:55 ` Jason Wang
2020-04-16 10:55 ` Eugenio Perez Martin
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=20200409170152-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=quintela@redhat.com \
--cc=rob.miller@broadcom.com \
--cc=virtio-dev@lists.oasis-open.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