From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, "Nemeth, Balazs" <balazs.nemeth@intel.com>
Subject: Re: [dpdk-dev] ixgbe vector mode not working.
Date: Wed, 25 Feb 2015 10:18:58 +0100 [thread overview]
Message-ID: <203551478.oOl1MzYCiU@xps13> (raw)
In-Reply-To: <20150224233651.5e27e791@urahara>
2015-02-24 23:36, Stephen Hemminger:
> On Wed, 25 Feb 2015 04:55:09 +0000
> "Liang, Cunming" <cunming.liang@intel.com> wrote:
>
> > Hi Stephen,
> >
> > I tried on the latest mater branch with testpmd.
> > 2 rxq and 2 txq as below, vector pmd on both rx and tx. I can't reproduced it.
> > I checked your log, on tx side, it looks the tx vector haven't enabled. (it shows vpmd on rx, spmd on tx).
> > Would you help to share the below params in your app ?
> > RX desc=128 - RX free threshold=32
> > TX desc=512 - TX free threshold=32
> > TX RS bit threshold=32 - TXQ flags=0xf01
> > As in your case which using 2 rxq and 1 txq, would you explain the traffic flow between them.
> > One thread polling packets from each rxq and send to the specified txq ?
>
> Basic thread model of application is same as examples/qos_sched.
>
> On ixgbe:
> RX desc = 4000 - RX free threshold=32
> TX desc = 512 - TX free threshold=0 so driver sets default of 32
>
> I was setting rx/tx conf but since examples don't went away from that.
>
> The whole RX/TX tuning parameters are a very poor programming model only
> a hardware engineer could love. Requiring the application to look at
> driver string and choose the magic parameter settings, is in my opnion
> an indication of using incorrect abstraction.
Yes, improvements are welcome.
prev parent reply other threads:[~2015-02-25 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 0:16 Stephen Hemminger
2015-02-25 4:55 ` Liang, Cunming
2015-02-25 7:36 ` Stephen Hemminger
2015-02-25 8:49 ` Liang, Cunming
2015-02-26 1:07 ` Stephen Hemminger
2015-02-28 3:33 ` Liang, Cunming
2015-03-05 19:09 ` Thomas Monjalon
2015-02-25 9:18 ` Thomas Monjalon [this message]
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=203551478.oOl1MzYCiU@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=balazs.nemeth@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).