From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Jayakumar, Muthurajan" <muthurajan.jayakumar@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example
Date: Wed, 15 Jul 2015 00:54:17 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8C68160@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1689423.VMbrg9M0mP@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, July 14, 2015 4:28 PM
> To: Jayakumar, Muthurajan
> Cc: dev@dpdk.org; Wu, Jingjing
> Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example
>
> 2015-07-14 08:20, Jayakumar, Muthurajan:
> > Can you please share as what is the benefit of removing l3fwd-vf example?
> > Customers have been using this very much.
> > Please let me know what is the disadvantage of keeping l3fwd-vf.
>
> What is the benefit of keeping an example which can be replaced?
>
> "Because VF multi-queues can be supported, l3fwd can run on vf."
>
> Removing some code is a nice goal from a maintenance point of view.
Yes, the l3fwd-vf example is almost the same as l3fwd, it is just used when VF can only support one queue.
Because VF multi-queues is supported, l3fwd running on vf is a better choice.
next prev parent reply other threads:[~2015-07-15 0:54 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 [this message]
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
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=9BB6961774997848B5B42BEC655768F8C68160@SHSMSX104.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=muthurajan.jayakumar@intel.com \
--cc=thomas.monjalon@6wind.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).