Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH S39 v2 01/15] ice: Validate config for SW DCB map
Date: Wed, 19 Feb 2020 19:37:32 +0000	[thread overview]
Message-ID: <ebef05a4d22e42b79d943e9b444c0b19@intel.com> (raw)
In-Reply-To: <20200213213059.33939-1-anthony.l.nguyen@intel.com>

> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Tony Nguyen
> Sent: Thursday, February 13, 2020 1:31 PM
> To: intel-wired-lan at lists.osuosl.org; pmenzel at molgen.mpg.de
> Subject: [Intel-wired-lan] [PATCH S39 v2 01/15] ice: Validate config for SW
> DCB map
> 
> From: Avinash Dayanand <avinash.dayanand@intel.com>
> 
> Validate the inputs for SW DCB config received either via lldptool or pcap file.
> And don't apply DCB for bad bandwidth inputs. Without this patch, any config
> having bad inputs will cause the loss of link making PF unusable even after
> driver reload. Recoverable only via system reboot.
> 
> Signed-off-by: Avinash Dayanand <avinash.dayanand@intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
> v2:
> - Allocate all bandwidth to TC0 if no TCs requested any bandwidth
> - Remove zero bandwidth check on non-TC0
> - Add message about reason for error and return from error immediately in
>   ice_dcb_bwchk()
> - Change a comment
> ---
>  drivers/net/ethernet/intel/ice/ice_dcb_lib.c | 40 ++++++++++++++++++++
> drivers/net/ethernet/intel/ice/ice_dcb_lib.h |  1 +
> drivers/net/ethernet/intel/ice/ice_dcb_nl.c  |  6 +++
>  3 files changed, 47 insertions(+)

Tested-by: Andrew Bowers <andrewx.bowers@intel.com>



      reply	other threads:[~2020-02-19 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 21:30 [Intel-wired-lan] [PATCH S39 v2 01/15] ice: Validate config for SW DCB map Tony Nguyen
2020-02-19 19:37 ` Bowers, AndrewX [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=ebef05a4d22e42b79d943e9b444c0b19@intel.com \
    --to=andrewx.bowers@intel.com \
    --cc=intel-wired-lan@osuosl.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