[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140217214716.GD7941@thin>
Date: Mon, 17 Feb 2014 13:47:16 -0800
From: Josh Triplett <josh@...htriplett.org>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, mingo@...nel.org,
laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
darren@...art.com, fweisbec@...il.com, oleg@...hat.com, sbw@....edu
Subject: Re: [PATCH tip/core/rcu 0/6] Documentation changes for 3.15
On Mon, Feb 17, 2014 at 01:26:25PM -0800, Paul E. McKenney wrote:
> Hello!
>
> This series provides a variety of documentation updates:
>
> 1. Update the documentation on actions to take to avoid frenetic
> call_rcu() invocations from exhausting memory, including a mention
> of internal-to-RCU avoidance measures.
>
> 2. Add a note to Documentation/memory-barriers.txt stating that
> ACCESS_ONCE() provides cache coherence for accesses to any
> single given variable.
>
> 3. Add an explicit statement that in control dependencies, the
> condition must include the load in question.
>
> 4. Add WQ_SYSFS workqueues as a work-offloading option in
> Documentation/kernel-per-CPU-kthreads.txt.
>
> 5. It turns out that some types of control dependencies require
> memory barriers, most notably when the exact same store is
> at the beginning of both the then-clause and the else-clause.
> Document this.
>
> 6. Fixups to RTFP.txt
I've replied to 1, 2, and 5 with comments. For 3, 4, and 6:
Reviewed-by: Josh Triplett <josh@...htriplett.org>
--
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