All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	netdev@vger.kernel.org
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>, Eric Dumazet <edumazet@google.com>,
	tglx@linutronix.de, Marc Kleine-Budde <mkl@pengutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next] net: sched: Avoid using yield() in a busy waiting loop
Date: Sat, 12 Oct 2019 22:14:17 +0300	[thread overview]
Message-ID: <8c3fad79-369a-403d-89fd-e54ab1b03643@cogentembedded.com> (raw)
In-Reply-To: <20191011171526.fon5npsxnarpn3qp@linutronix.de>

Hello!

On 10/11/2019 08:15 PM, Sebastian Andrzej Siewior wrote:

> From: Marc Kleine-Budde <mkl@pengutronix.de>
> 
> With threaded interrupts enabled, the interrupt thread runs as SCHED_RR
> with priority 50. If a user application with a higher priority preempts
> the interrupt thread and tries to shutdown the network interface then it
> will loop forever. The kernel will spin in the loop waiting for the
> device to become idle and the scheduler will never consider the
> interrupt thread because its priority is lower.
> 
> Avoid the problem by using by sleeping for a jiffy giving other tasks,

   So "using" or "sleeping"? :-)

> including the interrupt thread, a chance to run and make progress.
> 
> In the original thread it has been suggested to use wait_event() and
> properly waiting for the state to occur. DaveM explained that this would
> require to add expensive checks in the fast paths of packet processing.
> 
> Link: https://lkml.kernel.org/r/1393976987-23555-1-git-send-email-mkl@pengutronix.de
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> [bigeasy: Rewrite commit message, add comment, use
>           schedule_timeout_uninterruptible()]
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> 
> The old thread also pointed anoth yield() loop which was resolved by
> commit
>    845704a535e9b ("tcp: avoid looping in tcp_send_fin()")
> 
>  net/sched/sch_generic.c | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c
> index 17bd8f539bc7f..b27574f2c6b47 100644
> --- a/net/sched/sch_generic.c
> +++ b/net/sched/sch_generic.c
> @@ -1217,8 +1217,13 @@ void dev_deactivate_many(struct list_head *head)
>  
>  	/* Wait for outstanding qdisc_run calls. */
>  	list_for_each_entry(dev, head, close_list) {
> -		while (some_qdisc_is_busy(dev))
> -			yield();
> +		while (some_qdisc_is_busy(dev)) {
> +			/* wait_event() would avoid this sleep-loop but would
> +			 * require expesive checks in the fast paths of packet

   Expensive?

> +			 * processing which isn't worth it.
> +			 */
> +			schedule_timeout_uninterruptible(1);
> +		}
>  		/* The new qdisc is assigned at this point so we can safely
>  		 * unwind stale skb lists and qdisc statistics
>  		 */

MBR, Sergei

  reply	other threads:[~2019-10-12 19:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 17:15 [PATCH net-next] net: sched: Avoid using yield() in a busy waiting loop Sebastian Andrzej Siewior
2019-10-12 19:14 ` Sergei Shtylyov [this message]
2019-10-16  8:28   ` [PATCH net-next v2] " Sebastian Andrzej Siewior
2019-10-16 17:28     ` Cong Wang
2019-10-16 18:48       ` Sebastian Andrzej Siewior
2019-10-16 21:33         ` Cong Wang
2019-10-17 19:33     ` David Miller

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=8c3fad79-369a-403d-89fd-e54ab1b03643@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=xiyou.wangcong@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.