[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53EBA560.8030404@redhat.com>
Date: Wed, 13 Aug 2014 13:50:24 -0400
From: Rik van Riel <riel@...hat.com>
To: Peter Zijlstra <peterz@...radead.org>,
Oleg Nesterov <oleg@...hat.com>
CC: linux-kernel@...r.kernel.org,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
Frank Mayhar <fmayhar@...gle.com>,
Frederic Weisbecker <fweisbec@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Sanjay Rao <srao@...hat.com>,
Larry Woodman <lwoodman@...hat.com>
Subject: Re: [PATCH RFC] time: drop do_sys_times spinlock
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/13/2014 01:40 PM, Peter Zijlstra wrote:
> So the problem with the above is the lack of fwd progress; if
> there's enough clone()/exit() happening in the thread group (and
> the more CPUs the more possible), we'll keep repeating.
We can fall back to taking the lock if we circle around,
or if there is a writer active when we are in seqcount_read,
similar to what the semaphore (ipc/sem.c) code is doing.
read_seqbegin_or_lock would do the trick...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJT66VgAAoJEM553pKExN6D1lMH/3/+5vCSsVAyOVLi/xFb7lmt
BhRoMJO5MtDaNV32thh8kv9m1Q6r8FqtExUN6aZkTGj6Gp8nAnKFi0tR7na6nwfv
dlxCP9Q8ETiGhhE1jcJLOfv8lut5PzkR8LvorUHIU3v9wuZMZHEZB4dV/Uc6Ntsf
Ek4iT6QYUUGz8zgmPN4DWZ3k86vof3BOQjzFCaQMMTp4W2fGUVNpTEG+h9fHv42w
SzLwCUpj/9UQ2Y+V7rQki2bKtcXNjZoOFMdcNL9AsAaeAbSWQyxXCGf5ku2kXKS6
GnxgXNX2rDGhkL8g61ZB3hq1bbWkgPDte8run9wKI3OU1Z0Pg+oxpe0HFC5Hoag=
=SACY
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists