From: Jens Freimann <jfreimann@redhat.com>
To: dev@dpdk.org
Cc: tiwei.bie@intel.com, maxime.coquelin@redhat.com, Gavin.Hu@arm.com
Subject: [dpdk-dev] [PATCH v8 0/8] implement packed virtqueues
Date: Tue, 16 Oct 2018 11:01:26 +0200 [thread overview]
Message-ID: <20181016090134.29448-1-jfreimann@redhat.com> (raw)
This is a basic implementation of packed virtqueues as specified in the
Virtio 1.1 draft. A compiled version of the current draft is available
at https://github.com/oasis-tcs/virtio-docs.git (or as .pdf at
https://github.com/oasis-tcs/virtio-docs/blob/master/virtio-v1.1-packed-wd10.pdf
A packed virtqueue is different from a split virtqueue in that it
consists of only a single descriptor ring that replaces available and
used ring, index and descriptor pointers.
Each descriptor is readable and writable and has a flags field. These flags
will mark if a descriptor is available or used. To detect new available descriptors
even after the ring has wrapped, device and driver each have a
single-bit wrap counter that is flipped from 0 to 1 and vice versa every time
the last descriptor in the ring is used/made available.
v7->v8:
* move desc_is_used change to correct patch
* remove trailing newline
* correct xmit code, flags update and memory barrier
* move packed desc init to dedicated function, split
and packed variant
Jens Freimann (8):
net/virtio: vring init for packed queues
net/virtio: add packed virtqueue defines
net/virtio: add packed virtqueue helpers
net/virtio: dump packed virtqueue data
net/virtio: implement transmit path for packed queues
net/virtio: implement receive path for packed queues
net/virtio: add virtio send command packed queue support
net/virtio: enable packed virtqueues by default
drivers/net/virtio/virtio_ethdev.c | 154 ++++++--
drivers/net/virtio/virtio_ethdev.h | 5 +
drivers/net/virtio/virtio_pci.h | 7 +
drivers/net/virtio/virtio_ring.h | 110 +++++-
drivers/net/virtio/virtio_rxtx.c | 545 +++++++++++++++++++++++++++--
drivers/net/virtio/virtqueue.c | 23 ++
drivers/net/virtio/virtqueue.h | 42 ++-
7 files changed, 832 insertions(+), 54 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-16 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 9:01 Jens Freimann [this message]
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 1/8] net/virtio: vring init for packed queues Jens Freimann
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 2/8] net/virtio: add packed virtqueue defines Jens Freimann
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 3/8] net/virtio: add packed virtqueue helpers Jens Freimann
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 4/8] net/virtio: dump packed virtqueue data Jens Freimann
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 5/8] net/virtio: implement transmit path for packed queues Jens Freimann
2018-10-18 4:43 ` Tiwei Bie
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 6/8] net/virtio: implement receive " Jens Freimann
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 7/8] net/virtio: add virtio send command packed queue support Jens Freimann
2018-10-16 9:01 ` [dpdk-dev] [PATCH v8 8/8] net/virtio: enable packed virtqueues by default Jens Freimann
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=20181016090134.29448-1-jfreimann@redhat.com \
--to=jfreimann@redhat.com \
--cc=Gavin.Hu@arm.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.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;
as well as URLs for NNTP newsgroup(s).