From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] bond: disabling broadcast mode when dpdk is built without RTE_MBUF_REFCNT
Date: Wed, 22 Oct 2014 10:47:09 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8972262E993@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1413973724-14803-1-git-send-email-declan.doherty@intel.com>
Hi Declan,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Declan Doherty
> Sent: Wednesday, October 22, 2014 11:29 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] bond: disabling broadcast mode when dpdk is
> built without RTE_MBUF_REFCNT
>
> Link bonding broadcast mode requires refcnt parameter in the mbuf struct to
> allow efficient transmission of duplicated mbufs on slave ports.
>
> This patch disables broadcast mode when the complication option
> RTE_MBUF_REFCNT
> is disabled to allow clean building of the bonding library
>
>
> Signed-off-by: Declan Doherty <declan.doherty@intel.com>
> ---
> app/test/test_link_bonding.c | 9 ++++++++-
> lib/librte_pmd_bond/rte_eth_bond.h | 3 ++-
> lib/librte_pmd_bond/rte_eth_bond_args.c | 2 ++
> lib/librte_pmd_bond/rte_eth_bond_pmd.c | 12 ++++++++++++
> 4 files changed, 24 insertions(+), 2 deletions(-)
>
As suggested by Thomas in my other patch (disable ipv4/v6 fragmentation if RTE_MBUF_REFCNT=n),
it may be useful to include a warning in the link bonding Makefile, letting the user know
that broadcast mode is disabled due to that option not set.
Thanks,
Pablo
next prev parent reply other threads:[~2014-10-22 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 10:28 Declan Doherty
2014-10-22 10:47 ` De Lara Guarch, Pablo [this message]
2014-10-22 12:59 ` [dpdk-dev] [PATCH v2] " Declan Doherty
2014-10-22 13:54 ` Thomas Monjalon
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=E115CCD9D858EF4F90C690B0DCB4D8972262E993@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.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).