From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "Qiu, Michael" <michael.qiu@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Liu, Yong" <yong.liu@intel.com>,
"Cao, Waterman" <waterman.cao@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example
Date: Wed, 20 Apr 2016 12:46:46 +0200 [thread overview]
Message-ID: <4008817.HUC273QNcu@xps13> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836A6DCA7@irsmsx105.ger.corp.intel.com>
2015-08-04 17:12, Ananyev, Konstantin:
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiu, Michael
> > Actually, l3fwd works fine with fm10k vf.
> >
> > I don't know what's the exact reason of l3fwd-vf still in DPDK,
> > at least we could make full support for vf in l3fwd instead of another
> > sample with most code are the same compare with l3fwd.
>
> Right now, l3fwd is not able to work properly for cases where number of forwarding lcores
> exceeds number of tx queues on any active port.
> As an example:
> 2 forwarding lcores and a port with just 1 TX queue (e1000 legacy device).
>
> To make l3fwd work for such cases you need to add some sort of synchronisation on TX path.
> Which means one of 2 ways:
> either introduce different TX path into l3fwd (one with sync if legacy/virual device is used, another without)
> and select it on process startup/config phase,
> or sync overhead for fastpath.
Any news about removing l3fwd-vf example?
l3fwd has been reworked but l3fwd-power, l3fwd-vf and l3fwd-thread are
still based on the old l3fwd with APP_LOOKUP_METHOD compile-time flag.
next prev parent reply other threads:[~2016-04-20 10:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 7:57 Jingjing Wu
2015-07-14 8:20 ` Jayakumar, Muthurajan
2015-07-14 8:28 ` Thomas Monjalon
2015-07-15 0:54 ` Wu, Jingjing
2015-07-14 14:50 ` Zhang, Helin
2015-07-22 10:30 ` Thomas Monjalon
2015-07-22 14:51 ` Zhang, Helin
2015-07-22 15:01 ` Ananyev, Konstantin
2015-08-03 16:54 ` Thomas Monjalon
2015-08-03 17:02 ` Zhang, Helin
2015-08-03 17:08 ` Thomas Monjalon
2015-08-04 17:06 ` Qiu, Michael
2015-08-04 17:12 ` Ananyev, Konstantin
2016-04-20 10:46 ` Thomas Monjalon [this message]
2016-04-20 11:16 ` Ananyev, Konstantin
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=4008817.HUC273QNcu@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=michael.qiu@intel.com \
--cc=waterman.cao@intel.com \
--cc=yong.liu@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).