From: Robert Stonehouse <rstonehouse@solarflare.com>
To: Andy Lutomirski <luto@amacapital.net>,
Shradha Shah <sshah@solarflare.com>,
Edward Cree <ecree@solarflare.com>,
"Network Development" <netdev@vger.kernel.org>,
Solarflare linux maintainers <linux-net-drivers@solarflare.com>
Subject: Re: sfc: Please add rss_cpus=hyperthreads support
Date: Tue, 5 May 2015 14:48:45 +0100 [thread overview]
Message-ID: <5548CA3D.7010408@solarflare.com> (raw)
In-Reply-To: <CALCETrWpJMT-SfKKhjRfeNRrXS6C6+SUuzOCuSYwMZbMCqB+tA@mail.gmail.com>
On 02/05/15 01:03, Andy Lutomirski wrote:
> Can you please port the rss_cpus=hyperthreads feature from the
> OpenOnload driver to the upstream driver? The fact that sticking:
>
> options sfc rss_cpus=hyperthreads
>
> into modprobe.conf causes sfc to fail to load when OpenOnload isn't
> installed is incredibly annoying, and the option is genuinely useful.
Sure; I will make sure that happens soon.
I can see how that would be annoying.
Thanks for the suggestion.
Rob
next prev parent reply other threads:[~2015-05-05 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 0:03 sfc: Please add rss_cpus=hyperthreads support Andy Lutomirski
2015-05-05 13:48 ` Robert Stonehouse [this message]
2016-05-01 2:27 ` Andy Lutomirski
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=5548CA3D.7010408@solarflare.com \
--to=rstonehouse@solarflare.com \
--cc=ecree@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=sshah@solarflare.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;
as well as URLs for NNTP newsgroup(s).