Re: [PATCH RFC tip/core/rcu] Parallelize and economize NOCB kthread wakeups

[Rik van Riel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/02/2014 01:26 PM, Peter Zijlstra wrote:
> On Wed, Jul 02, 2014 at 10:08:38AM -0700, Paul E. McKenney wrote:
>> As were others, not that long ago.  Today is the first hint that
>> I got that you feel otherwise.  But it does look like the softirq
>> approach to callback processing needs to stick around for awhile
>> longer.  Nice to hear that softirq is now "sane and normal"
>> again, I guess.  ;-)
> 
> Nah, softirqs are still totally annoying :-)
> 
> So I've lost detail again, but it seems to me that on all CPUs that
> are actually getting ticks, waking tasks to process the RCU state
> is entirely over doing it. Might as well keep processing their RCU
> state from the tick as was previously done.

For CPUs that are not getting ticks (eg. because they are idle),
is it worth waking up anything on that CPU, or would it make more
sense to simply process their RCU callbacks on a different CPU,
if there aren't too many pending?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTtEGCAAoJEM553pKExN6D7t4IALdymyu0+/SdaXG73dfkzNKd
yJ3WJtJl1TV6JyejV747IRdKYfkuliZJ+99JZHtJ9dWvOoTtw19GqXXXVANlFpNE
8dQ4UTR6gDE1fRHnWKCdi0p8s3JwgZYdyhr0fKq7k09EXs+eJvDUTVVptBwLj36P
oaENzeONv5xkn3LS9cZVQATX1ZjpYiXjFUxblWoi/NJfSIlq81IkPj8ujaZ4f/6Q
6QLqymNbUGnF5n8v5gs8UqsP+fM3phsIJsT5m42hqnS9eKVwcw4T7UZ8UMFie+mC
hzy7vA0ClcdMWOMlRCSRbJMq0lDA0ej8acYpnj4Yz13wY2DIdTYVU38BbUE+iNA=
=Ia0S
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/