From: Eric Dumazet <eric.dumazet@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: restore correct batch limiting
Date: Thu, 18 Oct 2012 18:10:28 +0200 [thread overview]
Message-ID: <1350576628.32642.14.camel@edumazet-glaptop> (raw)
In-Reply-To: <20121018152543.GI2518@linux.vnet.ibm.com>
On Thu, 2012-10-18 at 08:25 -0700, Paul E. McKenney wrote:
> On Thu, Oct 18, 2012 at 02:44:50PM +0200, Eric Dumazet wrote:
> >
> > Having 2 billions callbacks on one cpu would be problematic, I really
> > hope nobody relies on this ;)
>
> Fair point! ;-)
>
> But just making everything long makes it quite easy to analyze.
>
> > I guess the 10/infinity switch should be smarter.
> >
> > something like the following maybe :
> >
> > rdp->blimit = max(blimit, rdp->qlen >> 6);
> >
> > (if queue is big, dont wait to hit 10000 before allowing more items to
> > be handled per round)
>
> The -rt guys would not be amused. :-(
>
> But for non-realtime use, increasing rcutree.blimit either at boot or
> via sysfs could make sense. It is also likely that I will move callback
> processing to a kthread at some point, which would allow some additional
> flexibility.
>
Ah, I now realize the loop can exceed blimit, but is it true for BH
variant ? (Not really a problem for 3.6/3.7 kernels, but prior ones)
if (++count >= bl &&
(need_resched() ||
(!is_idle_task(current) && !rcu_is_callbacks_kthread())))
break;
I wonder if ksoftirqd should be included as well...
> Furthermore, it would be easy to have one default for non-rt and another
> for -rt, if that would help.
>
> > Signed-off-by: Eric Dumazet <edumazet@google.com>
> >
> > Please dont forget stable teams. (3.2 + )
>
> Added both, please see below!
>
Seems fine to me, thanks Paul !
next prev parent reply other threads:[~2012-10-18 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 7:14 Eric Dumazet
2012-10-17 13:18 ` Hillf Danton
2012-10-17 14:01 ` Eric Dumazet
2012-10-18 11:58 ` Paul E. McKenney
2012-10-18 12:44 ` Eric Dumazet
2012-10-18 15:25 ` Paul E. McKenney
2012-10-18 16:10 ` Eric Dumazet [this message]
2012-10-18 16:35 ` Paul E. McKenney
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=1350576628.32642.14.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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
all inboxes | Powered by JetHome®