From: Bruce Richardson <bruce.richardson@intel.com>
To: Declan Doherty <declan.doherty@intel.com>
Cc: Eric Kinzie <ehkinzie@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] bond: inherit maximum rx packet length
Date: Mon, 20 Jun 2016 17:38:59 +0100 [thread overview]
Message-ID: <20160620163859.GA14348@bricha3-MOBL3> (raw)
In-Reply-To: <bcdddbe0-7f66-6ada-4459-beed945e76d0@intel.com>
On Fri, Jun 17, 2016 at 03:30:03PM +0100, Declan Doherty wrote:
> On 07/05/16 04:45, Eric Kinzie wrote:
> > Instead of a hard-coded maximum receive length, allow the bond interface
> > to inherit this limit from the slave interfaces. This allows
> > an application that uses jumbo frames to pass realistic values to
> > rte_eth_dev_configure without causing an error.
> >
> > Before the bond interface is configured, allow slaves with any
> > max_rx_pktlen to be added and remember the lowest of these values as
> > a candidate value. During dev_configure, set the bond device's
> > max_rx_pktlen to the candidate value. After this point only slaves
> > with a max_rx_pktlen greater or equal to that of the bonding device
> > can be added.
> >
> > If all slaves are removed, the bond device's pktlen is cleared.
> >
> >Signed-off-by: Eric Kinzie <ehkinzie@gmail.com>
> >---
> >
> ....
> >
>
> Acked-by: Declan Dohetry <declan.doherty@intel.com>
Applied to dpdk-next-net/rel_16_07, with one checkpatch fix and with title
corrected to pass check with check-git-log.sh
/Bruce
prev parent reply other threads:[~2016-06-20 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 17:23 [dpdk-dev] [PATCH] " Eric Kinzie
2016-04-26 10:51 ` Declan Doherty
2016-04-29 21:36 ` Eric Kinzie
2016-04-29 22:30 ` [dpdk-dev] [PATCH v2] " Eric Kinzie
2016-04-29 22:30 ` Eric Kinzie
2016-05-06 8:50 ` Declan Doherty
2016-05-07 3:45 ` [dpdk-dev] [PATCH v3] " Eric Kinzie
2016-05-07 3:45 ` Eric Kinzie
2016-06-17 14:30 ` Declan Doherty
2016-06-20 16:38 ` Bruce Richardson [this message]
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=20160620163859.GA14348@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ehkinzie@gmail.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).