linux-kernel - Re: [PATCH] 3/4 qrcu: add documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070103093951.GM11203@kernel.dk>
Date:	Wed, 3 Jan 2007 10:39:51 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Tomas Carnecky <tom@...ervice.com>
Cc:	linux-kernel@...r.kernel.org,
	Nick Piggin <nickpiggin@...oo.com.au>, akpm@...l.org
Subject: Re: [PATCH] 3/4 qrcu: add documentation

On Wed, Jan 03 2007, Tomas Carnecky wrote:
> Jens Axboe wrote:
> > diff --git a/Documentation/RCU/checklist.txt b/Documentation/RCU/checklist.txt
> > index f4dffad..36d6185 100644
> > --- a/Documentation/RCU/checklist.txt
> > +++ b/Documentation/RCU/checklist.txt
> > @@ -259,3 +259,16 @@ over a rather long period of time, but improvements are always welcome!
> >  
> >  	Note that, rcu_assign_pointer() and rcu_dereference() relate to
> >  	SRCU just as they do to other forms of RCU.
> > +
> > +14.	QRCU is very similar to SRCU, but features very fast grace-period
> > +	processing at the expense of heavier-weight read-side operations.
> > +	The correspondance between QRCU and SRCU is as follows:
> > +
> > +		QRCU			SRCU
> > +
> > +		struct qrcu_struct	struct srcu_struct
> > +		init_qrcu_struct()	init_srcu_struct()
> > +		cleanup_qrcu_struct()	cleanup_srcu_struct()
> > +		qrcu_read_lock()	srcu_read_lock()
> > +		qrcu_read-unlock()	srcu_read_unlock()
> 
> A small typo: qrcu_read_unlock()

Indeed, thanks, I'll update the repo.

-- 
Jens Axboe

-
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/