From: Bruce Richardson <bruce.richardson@intel.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/2] enic: determine max egress packet size and max MTU
Date: Wed, 29 Jun 2016 11:01:33 +0100 [thread overview]
Message-ID: <20160629100132.GD4720@bricha3-MOBL3> (raw)
In-Reply-To: <1466807368-7215-1-git-send-email-johndale@cisco.com>
On Fri, Jun 24, 2016 at 03:29:27PM -0700, John Daley wrote:
> Pull in common VNIC code which enables querying for max egress
> packet size with newer firmware via a device command. If the
> field is non-zero, it is the max egress packet size. If it is
> 0, the default value (9022) can safely be assumed. The value
> for 1300 series VICS using firmware versions >= 3.1.2 for blade
> series and >= 2.0.13 for rack series servers is 9208.
>
> Tx buffers can be emitted only if they are less than the max egress
> packet size regardless of the MTU setting (the MTU is advisory).
> The max egress packet size can used to determine the upper limit
> of the MTU since the enic can also receive packets of size greater
> than max egress packet size. A max_mtu variable is added with
> a value of max egress packet size minus L2 header size.
>
> The default MTU is set via the CIMC/UCSM management interface and
> currently allows value up to 9000. If the value is changed, the
> host must be reboot. To avoid the reboot and allow MTU values
> up to the max capability of the NIC, MTU update capability will
> be added with a max value capped by max_mtu.
>
> Signed-off-by: John Daley <johndale@cisco.com>
> ---
> v2: Squished patch 1/4 and 2/4 into one. Tried to do a little
> better explanaiton of the intent of the patch in the commit
> message.
>
Patchset applied to dpdk-next-net/rel_16_07
/Bruce
next prev parent reply other threads:[~2016-06-29 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 5:22 [PATCH 0/4] enic: enable MTU update callback John Daley
2016-06-17 5:22 ` [PATCH 1/4] enic: enable NIC max packet size discovery John Daley
2016-06-24 10:56 ` Bruce Richardson
2016-06-17 5:22 ` [PATCH 2/4] enic: set the max allowed MTU for the NIC John Daley
2016-06-24 10:59 ` Bruce Richardson
2016-06-24 11:01 ` Bruce Richardson
2016-06-24 22:29 ` [PATCH v2 1/2] enic: determine max egress packet size and max MTU John Daley
2016-06-24 22:29 ` [PATCH v2 2/2] enic: add an update MTU function for non-Rx scatter mode John Daley
2016-06-29 10:01 ` Bruce Richardson [this message]
2016-06-24 22:42 ` [PATCH 2/4] enic: set the max allowed MTU for the NIC John Daley (johndale)
2016-06-17 5:22 ` [PATCH 3/4] enic: add an update MTU function for non-Rx scatter mode John Daley
2016-06-17 5:22 ` [PATCH 4/4] doc: add MTU update to feature matrix for enic John Daley
2016-06-24 11:01 ` Bruce Richardson
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=20160629100132.GD4720@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.