Netdev List
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: Samuel Mendoza-Jonas <sam@mendozajonas.com>, netdev@vger.kernel.org
Cc: openbmc@lists.ozlabs.org,
	"David S . Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, Brian J King <bjking1@us.ibm.com>
Subject: Re: [PATCH net-next] net/ncsi: Don't take any action on HNCDSC AEN
Date: Fri, 15 Dec 2017 14:06:45 +0800	[thread overview]
Message-ID: <fe1916de-5eb0-6084-c528-822d06c652e0@ozlabs.org> (raw)
In-Reply-To: <20171215051640.10926-1-sam@mendozajonas.com>

Hi Sam,

> The current HNCDSC handler takes the status flag from the AEN packet and
> will update or change the current channel based on this flag and the
> current channel status.
> 
> However the flag from the HNCDSC packet merely represents the host link
> state. While the state of the host interface is potentially interesting
> information it should not affect the state of the NCSI link. Indeed the
> NCSI specification makes no mention of any recommended action related to
> the host network controller driver state.

Yep, sounds good to me. If the link status does change, we should see an
separate AEN for that event.

Acked-by: Jeremy Kerr <jk@ozlabs.org>

However: we're looking at some behaviour of Broadcom NICs at the moment,
where the phy will be reset on link change events. We'd want to make
sure that we're not just seeing the HNCDSC events for that too. I'd
suggest we also get an Ack from Brian (CCed) to make sure we're not
breaking that case.

Cheers,


Jeremy

  reply	other threads:[~2017-12-15  6:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15  5:16 [PATCH net-next] net/ncsi: Don't take any action on HNCDSC AEN Samuel Mendoza-Jonas
2017-12-15  6:06 ` Jeremy Kerr [this message]
2017-12-18 19:50 ` David Miller

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=fe1916de-5eb0-6084-c528-822d06c652e0@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=bjking1@us.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sam@mendozajonas.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