DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ravi Kerur <rkerur@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Q on IXGBE and I40E vector Tx processing
Date: Sun, 16 Apr 2017 12:33:39 -0700	[thread overview]
Message-ID: <CAFb4SLCXFWr6kkc7NK+8+yvoV4nL3EpOWe_99soTXOqoR=XATg@mail.gmail.com> (raw)
In-Reply-To: <CAFb4SLDctKrqBSRZEc5MgsAv0bGKdE9_M8UeFdoUb4nEY=Hm1w@mail.gmail.com>

Hi,

The reason I am asking I because I have tried different combinations of
scalar and vector Tx and Rx processing for both IXGBE and I40E with
following results

1. Vector Rx and Vector Tx gives best performance but can only support
packet size of less than or equal to 2048 bytes

2. Scalar Rx and Scalar Tx works for all packet size but with degraded
performance

3. Vector Rx and Scalar Tx (with certain PMD configuration) works fine
(performance doesn't meet '1') but it has an inherent bug for packet size
8192 bytes as PMD stops packet processing

>From the code I see both IXGBE and I40E can support scattered vector Rx, I
am curious to know any obvious reasons scattered vector Tx support is left
out and does it make sense to implement it?

If it makes sense to implement scattered vector Tx and Intel team hasn't
worked on it I would like to make an attempt at it so kindly let me know.

Thanks.

On Fri, Apr 14, 2017 at 10:35 AM, Ravi Kerur <rkerur@gmail.com> wrote:

> Hi,
>
> We are using dpdk 16.04 and by looking at the ixgbe and
> i40e(i40e_xmit_pkts_vec) and ixgbe(ixgbe_xmit_pkts_vec) driver vector tx
> processing code I see they both don't handle scattered packet processing.
> For any packets greater than 2048 bytes which will basically contain
> multiple rte_mbuf segs vector tx processing cannot be used.
>
> Any reasons why vector tx for both ixgbe and i40e doesn't support
> scattered or multiple mbuf segments processing?
>
> Thanks.
>

  reply	other threads:[~2017-04-16 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 17:35 Ravi Kerur
2017-04-16 19:33 ` Ravi Kerur [this message]
2017-04-16 22:26   ` Ananyev, Konstantin
2017-04-17 23:47     ` Ravi Kerur

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='CAFb4SLCXFWr6kkc7NK+8+yvoV4nL3EpOWe_99soTXOqoR=XATg@mail.gmail.com' \
    --to=rkerur@gmail.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).