[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070625214246.GC2051@elf.ucw.cz>
Date: Mon, 25 Jun 2007 23:42:46 +0200
From: Pavel Machek <pavel@....cz>
To: Oleg Nesterov <oleg@...sign.ru>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Andrew Morton <akpm@...ux-foundation.org>,
Nigel Cunningham <nigel@...el.suspend2.net>,
Uli Luckas <u.luckas@...d.de>, linux-kernel@...r.kernel.org
Subject: Re: synchronize_qrcu_timeout()
On Mon 2007-06-25 19:49:57, Oleg Nesterov wrote:
> On 06/25, Oleg Nesterov wrote:
> >
> > On 06/25, Paul E. McKenney wrote:
> > >
> > > On Mon, Jun 25, 2007 at 02:43:32PM +0400, Oleg Nesterov wrote:
> > > >
> > > > Sadly, you can't use srcu/qrcu because it doesn't handle timeouts.
> > >
> > > Interesting... So the thought is to have a synchronize_srcu_timeout()
> > > or something similar that waited for a grace period to elapse or for
> > > a timeout to expire, whichever comes first? It should not be too hard
> > > to arrange something, if needed.
> >
> > Yes. As for qrcu (see http://marc.info/?t=116484476500001), I think it is easy.
> > First, we add "int interrupted" into struct qrcu_struct, then something like this
>
> Even simpler, we don't need ->interrupted.
>
> long synchronize_qrcu_timeout(struct qrcu_struct *qp, long tout)
> {
> int idx, prv;
Could we get less encrypted variable names? tout? Yes, I can decipher it.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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