From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "Kovacevic, Marko" <marko.kovacevic@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix link bonding pmd typo in prog guide
Date: Fri, 19 Jan 2018 01:59:13 +0000 [thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A8B028415@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <6DC05C7C5F25994B81B3F2F214251F66332574@IRSMSX104.ger.corp.intel.com>
Thanks, V3 will be coming soon.
> -----Original Message-----
> From: Kovacevic, Marko
> Sent: Monday, January 15, 2018 7:22 PM
> To: Yang, Zhiyong <zhiyong.yang@intel.com>; dev@dpdk.org
> Cc: Mcnamara, John <john.mcnamara@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] doc: fix link bonding pmd typo in prog guide
>
> Actually just one more change it would be better as "similar capabilities"
> instead of "the similar capabilities"
>
> The Link Bonding PMD library(librte_pmd_bond) supports bonding of groups
> of ``rte_eth_dev`` ports of the same speed and duplex to provide similar
> capabilities to that found in Linux bonding driver to allow the aggregation of
> multiple (slave) NICs into a single logical interface between a server and a
> switch. The new bonded PMD will then process these interfaces based on
> the mode of operation specified to provide support for features such
>
> Marko K.
next prev parent reply other threads:[~2018-01-19 1:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 6:32 Zhiyong Yang
2018-01-12 9:37 ` Kovacevic, Marko
2018-01-12 10:56 ` Yang, Zhiyong
2018-01-15 11:21 ` Kovacevic, Marko
2018-01-19 1:59 ` Yang, Zhiyong [this message]
2018-01-12 10:40 ` [dpdk-dev] [PATCH v2] doc: fix link bonding PMD " Zhiyong Yang
2018-01-15 11:23 ` Kovacevic, Marko
2018-01-19 2:21 ` [dpdk-dev] [PATCH v3] " Zhiyong Yang
2018-01-19 19:43 ` [dpdk-dev] [dpdk-stable] " 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=E182254E98A5DA4EB1E657AC7CB9BD2A8B028415@BGSMSX101.gar.corp.intel.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).