From: Chas Williams <3chas3@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, "John W. Linville" <linville@tuxdriver.com>,
"Charles (Chas) Williams" <ciwillia@brocade.com>,
Chas Williams <chas3@att.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/af_packet: make bypass configurable
Date: Thu, 5 Oct 2017 10:15:09 -0400 [thread overview]
Message-ID: <CAG2-GkkgmBcUSx81Xv4uC=7tmg2TOnjOZPoeaKmpasdH_4=eAg@mail.gmail.com> (raw)
In-Reply-To: <0b7b3864-7594-5737-8f23-8dd8420a1c54@intel.com>
On Wed, Sep 20, 2017 at 9:21 AM, Ferruh Yigit <ferruh.yigit@intel.com>
wrote:
> On 9/19/2017 10:45 PM, Chas Williams wrote:
> > From: "Charles (Chas) Williams" <ciwillia@brocade.com>
> >
> > In certain situations, low speed interfaces, it may be desirable to
> > have the flow control provided by the kernel queueing disciplines.
>
> Out of curiosity, do you have any compression of performance numbers
> with and without qdisc?
>
I had some time to test this. I didn't see any loss in performance but the
interfaces
I am using only go about 200-300Mbps. it likely makes a difference if you
can go
much much faster.
next prev parent reply other threads:[~2017-10-05 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 21:21 [dpdk-dev] [PATCH] " Chas Williams
2017-09-19 21:45 ` [dpdk-dev] [PATCH v2] " Chas Williams
2017-09-20 9:59 ` Luca Boccassi
2017-09-20 13:21 ` Ferruh Yigit
2017-10-05 14:15 ` Chas Williams [this message]
2017-09-21 3:25 ` [dpdk-dev] [PATCH v3] " Chas Williams
2017-09-21 9:34 ` Ferruh Yigit
2017-09-21 9:57 ` [dpdk-dev] [PATCH v4] " Chas Williams
2017-09-21 14:43 ` Ferruh Yigit
2017-09-22 17:44 ` Ferruh Yigit
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='CAG2-GkkgmBcUSx81Xv4uC=7tmg2TOnjOZPoeaKmpasdH_4=eAg@mail.gmail.com' \
--to=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=ciwillia@brocade.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=linville@tuxdriver.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).