From: Simon Horman <horms@verge.net.au>
To: Simon Horman <simon.horman@netronome.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net] nfp: do not update MTU from BH in flower app
Date: Fri, 11 Aug 2017 10:10:24 +0200 [thread overview]
Message-ID: <20170811081021.GA12975@verge.net.au> (raw)
In-Reply-To: <1502438823-12830-1-git-send-email-simon.horman@netronome.com>
On Fri, Aug 11, 2017 at 10:07:03AM +0200, Simon Horman wrote:
> The Flower app may receive a request to update the MTU of a representor
> netdev upon receipt of a control message from the firmware. This requires
> the RTNL lock which needs to be taken outside of the packet processing
> path.
>
> As a handling of this correctly seems a little to invasive for a fix simply
> skip setting the MTU for now.
Sorry, please ignore this.
It is not against net as it claims. I will post a version against that tree.
prev parent reply other threads:[~2017-08-11 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 8:07 [PATCH net] nfp: do not update MTU from BH in flower app Simon Horman
2017-08-11 8:10 ` Simon Horman [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=20170811081021.GA12975@verge.net.au \
--to=horms@verge.net.au \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.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