From: David Miller <davem@davemloft.net>
To: ecree@solarflare.com
Cc: linux-net-drivers@solarflare.com, netdev@vger.kernel.org
Subject: Re: [PATCH net 2/2] sfc: limit ARFS workitems in flight per channel
Date: Thu, 12 Apr 2018 11:11:32 -0400 (EDT) [thread overview]
Message-ID: <20180412.111132.159310781108534969.davem@davemloft.net> (raw)
In-Reply-To: <d3bd9e31-5247-8032-8f35-c85d3728c32e@solarflare.com>
From: Edward Cree <ecree@solarflare.com>
Date: Thu, 12 Apr 2018 15:02:50 +0100
> A misconfigured system (e.g. with all interrupts affinitised to all CPUs)
> may produce a storm of ARFS steering events. With the existing sfc ARFS
> implementation, that could create a backlog of workitems that grinds the
> system to a halt. To prevent this, limit the number of workitems that
> may be in flight for a given SFC device to 8 (EFX_RPS_MAX_IN_FLIGHT), and
> return EBUSY from our ndo_rx_flow_steer method if the limit is reached.
> Given this limit, also store the workitems in an array of slots within the
> struct efx_nic, rather than dynamically allocating for each request.
>
> Signed-off-by: Edward Cree <ecree@solarflare.com>
I don't think this behavior is all that great.
If you really have to queue up these operations because they take a long
time, I think it is better to enter a synchronous mode and sleep once
you hit this in-flight limit of 8.
Either that or make the expiration work smarter when it has lots of events
to process.
next prev parent reply other threads:[~2018-04-12 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 14:00 [PATCH net 0/2] sfc: couple of ARFS fixes Edward Cree
2018-04-12 14:02 ` [PATCH net 1/2] sfc: insert ARFS filters with replace_equal=true Edward Cree
2018-04-12 14:02 ` [PATCH net 2/2] sfc: limit ARFS workitems in flight per channel Edward Cree
2018-04-12 15:11 ` David Miller [this message]
2018-04-12 15:24 ` Edward Cree
2018-04-12 15:33 ` David Miller
2018-04-13 12:36 ` Edward Cree
2018-04-13 14:45 ` David Miller
2018-04-13 14:52 ` Edward Cree
2018-04-13 15:03 ` David Miller
2018-04-13 15:59 ` Edward Cree
2018-04-13 16:14 ` David Miller
2018-04-13 16:24 ` Edward Cree
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=20180412.111132.159310781108534969.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
/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