From: Stephen Hemminger <stephen@networkplumber.org>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 3/4] virtio: use indirect ring elements
Date: Sun, 6 Sep 2015 11:42:02 -0700 [thread overview]
Message-ID: <20150906114202.634c8602@urahara> (raw)
In-Reply-To: <F52918179C57134FAEC9EA62FA2F962511CFDA18@shsmsx102.ccr.corp.intel.com>
On Sun, 6 Sep 2015 08:36:10 +0000
"Ouyang, Changchun" <changchun.ouyang@intel.com> wrote:
> > -----Original Message-----
> > From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > Sent: Saturday, September 5, 2015 4:58 AM
> > To: Xie, Huawei; Ouyang, Changchun
> > Cc: dev@dpdk.org; Stephen Hemminger
> > Subject: [PATCH 3/4] virtio: use indirect ring elements
> >
> > The virtio ring in QEMU/KVM is usually limited to 256 entries and the normal
> > way that virtio driver was queuing mbufs required nsegs + 1 ring elements.
> > By using the indirect ring element feature if available, each packet will take
> > only one ring slot even for multi-segment packets.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> > drivers/net/virtio/virtio_ethdev.c | 11 +++++---
> > drivers/net/virtio/virtio_ethdev.h | 3 ++-
> > drivers/net/virtio/virtio_rxtx.c | 51 ++++++++++++++++++++++++++++++-
> > -------
> > drivers/net/virtio/virtqueue.h | 8 ++++++
> > 4 files changed, 57 insertions(+), 16 deletions(-)
> >
> > diff --git a/drivers/net/virtio/virtio_ethdev.c
> > b/drivers/net/virtio/virtio_ethdev.c
> > index 465d3cd..bcfb87b 100644
> > --- a/drivers/net/virtio/virtio_ethdev.c
> > +++ b/drivers/net/virtio/virtio_ethdev.c
> > @@ -359,12 +359,15 @@ int virtio_dev_queue_setup(struct rte_eth_dev
> > *dev,
> > if (queue_type == VTNET_TQ) {
>
> Do we also need implement indirect ring elements for RX path?
No. Look at Linux driver, indirect elements are never passed to RX driver.
next prev parent reply other threads:[~2015-09-06 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 20:58 [dpdk-dev] [PATCH 0/4] RFC virtio performance enhancement and cleanups Stephen Hemminger
2015-09-04 20:58 ` [dpdk-dev] [PATCH 1/4] virtio: clean up space checks on xmit Stephen Hemminger
2015-09-04 20:58 ` [dpdk-dev] [PATCH 2/4] virtio: don't use unlikely for normal tx stuff Stephen Hemminger
2015-09-04 20:58 ` [dpdk-dev] [PATCH 3/4] virtio: use indirect ring elements Stephen Hemminger
2015-09-06 8:36 ` Ouyang, Changchun
2015-09-06 18:42 ` Stephen Hemminger [this message]
2015-09-06 8:40 ` Ouyang, Changchun
2015-09-06 18:43 ` Stephen Hemminger
2015-09-07 7:24 ` Thomas Monjalon
2015-09-04 20:58 ` [dpdk-dev] [PATCH 4/4] virtio: use any layout on transmit Stephen Hemminger
2015-09-07 7:04 ` [dpdk-dev] [PATCH 0/4] RFC virtio performance enhancement and cleanups Thomas Monjalon
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=20150906114202.634c8602@urahara \
--to=stephen@networkplumber.org \
--cc=changchun.ouyang@intel.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).