From: Jakub Kicinski <kuba@kernel•org>
To: Edward Cree <ecree.xilinx@gmail•com>
Cc: Joe Damato <jdamato@fastly•com>,
netdev@vger•kernel.org, saeedm@nvidia•com, tariqt@nvidia•com,
ecree@solarflare•com, andrew@lunn•ch, davem@davemloft•net,
leon@kernel•org, pabeni@redhat•com, bhutchings@solarflare•com,
arnd@arndb•de, linux-kernel@vger•kernel.org
Subject: Re: [net 0/2] rxfh with custom RSS fixes
Date: Thu, 27 Jul 2023 08:49:51 -0700 [thread overview]
Message-ID: <20230727084951.1e4d3279@kernel.org> (raw)
In-Reply-To: <f565a8d6-e3b8-96d1-a7ac-212c64c60b1c@gmail.com>
On Tue, 25 Jul 2023 09:40:24 +0100 Edward Cree wrote:
> More generally the status of my RSS work is that I've been umming
> and ahhing about that mutex you didn't like (I still think it's
> the Right Thing) so I've not made much progress with it.
I had a look at the code again, and I don't think the mutex is a deal
breaker. More of an aesthetic thing, so to speak. If you strongly
prefer to keep the mutex that's fine.
prev parent reply other threads:[~2023-07-27 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 15:06 [net 0/2] rxfh with custom RSS fixes Joe Damato
2023-07-23 15:06 ` [net 1/2] net: ethtool: Unify ETHTOOL_{G,S}RXFH rxnfc copy Joe Damato
2023-07-24 19:27 ` Edward Cree
2023-07-23 15:06 ` [net 2/2] net/mlx5: Fix flowhash key set/get for custom RSS Joe Damato
2023-07-25 9:59 ` Tariq Toukan
2023-07-26 8:28 ` Joe Damato
2023-07-24 19:27 ` [net 0/2] rxfh with custom RSS fixes Edward Cree
2023-07-24 21:36 ` Joe Damato
2023-07-24 22:08 ` Jakub Kicinski
2023-07-25 8:40 ` Edward Cree
2023-07-25 20:47 ` Joe Damato
2023-07-27 15:49 ` Jakub Kicinski [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=20230727084951.1e4d3279@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=arnd@arndb$(echo .)de \
--cc=bhutchings@solarflare$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ecree.xilinx@gmail$(echo .)com \
--cc=ecree@solarflare$(echo .)com \
--cc=jdamato@fastly$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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