From: David Miller <davem@davemloft.net>
To: EladN@gilat.com
Cc: netdev@vger.kernel.org
Subject: Re: Kernel 4.6.7-rt14 kernel workqueue lockup - rtnl deadlock plus syscall endless loop
Date: Tue, 17 Jan 2017 14:05:52 -0500 (EST) [thread overview]
Message-ID: <20170117.140552.539738967862859087.davem@davemloft.net> (raw)
In-Reply-To: <AM5PR0701MB1873F82D61AF17A09F2B0E26A07C0@AM5PR0701MB1873.eurprd07.prod.outlook.com>
From: Elad Nachman <EladN@gilat.com>
Date: Tue, 17 Jan 2017 18:15:19 +0000
> Any thought about limiting the amount of busy polling? Say if more
> than X polls are done within a jiffy, then at least for preemptable
> kernels you can sleep for a jiffy inside the syscall to yield the
> CPU for a while?
We cannot yield there, because we must return immediately from this
context in order to drop the sysctl locks and references.
next prev parent reply other threads:[~2017-01-17 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 17:39 Kernel 4.6.7-rt14 kernel workqueue lockup - rtnl deadlock plus syscall endless loop Elad Nachman
2017-01-17 17:53 ` Stephen Hemminger
2017-01-17 17:57 ` David Miller
2017-01-17 18:15 ` Elad Nachman
2017-01-17 19:05 ` David Miller [this message]
2017-01-18 9:57 ` Elad Nachman
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=20170117.140552.539738967862859087.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=EladN@gilat.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