From: "Qiu, Michael" <michael.qiu@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"Liu, Yong" <yong.liu@intel.com>,
"Cao, Waterman" <waterman.cao@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example
Date: Tue, 4 Aug 2015 17:06:09 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286046FF05F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A898517@SHSMSX104.ccr.corp.intel.com>
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.
Thanks,
Michael
On 2015/7/22 7:51, Zhang, Helin wrote:
Marvin/Waterman
Could you help to check if l3fwd is good enough for all cases (1g/10/40g, PF and VF, single queue/multiple queue)?
We aim to remove l3fwd-vf to reduce an example application which is not so necessary.
Thank you!
Regards,
Helin
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Wednesday, July 22, 2015 3:30 AM
To: Zhang, Helin
Cc: dev@dpdk.org<mailto:dev@dpdk.org>; Wu, Jingjing
Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example
2015-07-14 14:50, Zhang, Helin:
From: Wu, Jingjing
Because VF multi-queues can be supported, l3fwd can run on vf.
Suggest to remove the l3fwd-vf example.
Totally agree with this!
But we need the confirmation from validation guys of that l3fwd works
quite well on VF with all NICs (e.g. i350, 82599, x550, xl710, and fm10k).
Helin, any new from validation?
next prev parent reply other threads:[~2015-08-04 17:06 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 [this message]
2015-08-04 17:12 ` Ananyev, Konstantin
2016-04-20 10:46 ` Thomas Monjalon
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=533710CFB86FA344BFBF2D6802E60286046FF05F@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=thomas.monjalon@6wind.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).