From: Jakub Kicinski <kuba@kernel.org>
To: Matt Corallo <linux-wired-list@bluematt.me>
Cc: Nick Lowe <nick.lowe@gmail.com>,
netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
jesse.brandeburg@intel.com, intel-wired-lan@lists.osuosl.org,
davem@davemloft.net
Subject: Re: [PATCH net] igb: Enable RSS for Intel I211 Ethernet Controller
Date: Mon, 1 Feb 2021 08:47:47 -0800 [thread overview]
Message-ID: <20210201084747.2cb64c3f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <379d4ef3-02e5-f08a-1b04-21848e11a365@bluematt.me>
On Sun, 31 Jan 2021 18:17:11 -0500 Matt Corallo wrote:
> Given this fixes a major (albeit ancient) performance regression, is
> it not a candidate for backport? It landed on Tony's dev-queue branch
> with a Fixes tag but no stable CC.
Tony's tree needs to get fed into net, then net into Linus's tree and
then we can do the backport :(
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net] igb: Enable RSS for Intel I211 Ethernet Controller
Date: Mon, 1 Feb 2021 08:47:47 -0800 [thread overview]
Message-ID: <20210201084747.2cb64c3f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <379d4ef3-02e5-f08a-1b04-21848e11a365@bluematt.me>
On Sun, 31 Jan 2021 18:17:11 -0500 Matt Corallo wrote:
> Given this fixes a major (albeit ancient) performance regression, is
> it not a candidate for backport? It landed on Tony's dev-queue branch
> with a Fixes tag but no stable CC.
Tony's tree needs to get fed into net, then net into Linus's tree and
then we can do the backport :(
next prev parent reply other threads:[~2021-02-01 16:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 22:25 [PATCH net] igb: Enable RSS for Intel I211 Ethernet Controller Nick Lowe
2020-12-21 22:25 ` [Intel-wired-lan] " Nick Lowe
2021-01-31 23:17 ` Matt Corallo
2021-01-31 23:17 ` [Intel-wired-lan] " Matt Corallo
2021-02-01 16:47 ` Jakub Kicinski [this message]
2021-02-01 16:47 ` Jakub Kicinski
2021-02-01 18:32 ` Nguyen, Anthony L
2021-02-01 18:32 ` [Intel-wired-lan] " Nguyen, Anthony L
2021-02-01 19:45 ` Jakub Kicinski
2021-02-01 19:45 ` [Intel-wired-lan] " Jakub Kicinski
2021-02-01 20:06 ` Nick Lowe
2021-02-01 20:06 ` [Intel-wired-lan] " Nick Lowe
2021-02-01 20:21 ` Matt Corallo
2021-02-01 20:21 ` [Intel-wired-lan] " Matt Corallo
2021-02-01 20:23 ` Nick Lowe
2021-02-01 20:23 ` [Intel-wired-lan] " Nick Lowe
2021-02-01 20:33 ` Jakub Kicinski
2021-02-01 20:33 ` [Intel-wired-lan] " Jakub Kicinski
2021-05-03 12:32 ` Nick Lowe
2021-05-03 12:32 ` [Intel-wired-lan] " Nick Lowe
2021-05-03 18:30 ` Jakub Kicinski
2021-05-03 18:30 ` [Intel-wired-lan] " Jakub Kicinski
2021-05-03 19:53 ` Stable inclusion request - " Nick Lowe
2021-05-03 19:53 ` [Intel-wired-lan] " Nick Lowe
2021-05-04 4:43 ` Greg KH
2021-05-04 4:43 ` [Intel-wired-lan] " Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 19:15 [PATCH net] " Nick Lowe
2020-12-21 22:11 ` Jakub Kicinski
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=20210201084747.2cb64c3f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-wired-list@bluematt.me \
--cc=netdev@vger.kernel.org \
--cc=nick.lowe@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 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.