From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, brouer@redhat.com,
alexander.duyck@gmail.com, oss-drivers@netronome.com
Subject: Re: [RFC] net: bump the default number of RSS queues
Date: Wed, 4 Apr 2018 17:08:45 -0700 [thread overview]
Message-ID: <20180404170845.77c54f38@cakuba.netronome.com> (raw)
In-Reply-To: <3f6f40f3-cca2-0f43-8940-05003da88524@gmail.com>
On Tue, 3 Apr 2018 17:20:49 -0700, Eric Dumazet wrote:
> On 04/03/2018 05:14 PM, Jakub Kicinski wrote:
> > Some popular NIC vendors are not adhering to
> > netif_get_num_default_rss_queues() which leads to users being
> > surprised and filing bugs :) Bump the number of default RX
> > queues to something more reasonable for modern machines.
> >
> > Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> > ---
> > I'm mostly wondering what's the policy on this default? When
> > should it be applied? Why was 8 chosen as the default? We
> > can abandon using netif_get_num_default_rss_queues() for the
> > nfp but I wonder what's the correct course of action here...
> > Should new drivers use netif_get_num_default_rss_queues() for
> > example?
> >
> > include/linux/netdevice.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> > index 2a2d9cf50aa2..26fe145ada2a 100644
> > --- a/include/linux/netdevice.h
> > +++ b/include/linux/netdevice.h
> > @@ -3260,7 +3260,7 @@ static inline unsigned int get_netdev_rx_queue_index(
> > }
> > #endif
> >
> > -#define DEFAULT_MAX_NUM_RSS_QUEUES (8)
> > +#define DEFAULT_MAX_NUM_RSS_QUEUES (64)
> > int netif_get_num_default_rss_queues(void);
>
> There is no evidence having so many queues is beneficial.
>
> Too many queues -> lots of overhead in many cases.
>
> So I would rather not touch this, unless you can present good numbers ;)
Thank you for the comment! I don't have convincing number it was more
of a matter of consistency :)
Now I think I forgot about aRFS, when aRFS support for the nfp is added
we will probably start ignoring the default as well.
prev parent reply other threads:[~2018-04-05 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 0:14 [RFC] net: bump the default number of RSS queues Jakub Kicinski
2018-04-04 0:20 ` Eric Dumazet
2018-04-05 0:08 ` 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=20180404170845.77c54f38@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alexander.duyck@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@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