From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Allen Simpson Subject: [PATCH resent] Documentation: rw_lock lessons learned Date: Tue, 10 Nov 2009 14:55:44 -0500 Message-ID: <4AF9C540.5090403@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------040700040300000504090809" Cc: Eric Dumazet , "Paul E. McKenney" To: Linux Kernel Developers , Linux Kernel Network Developers Return-path: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org This is a multi-part message in MIME format. --------------040700040300000504090809 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In recent weeks, two different network projects erroneously strayed down the rw_lock path. Update the Documentation based upon comments in those threads. Signed-off-by: William.Allen.Simpson@gmail.com --- Documentation/spinlocks.txt | 14 ++++++++++++++ 1 files changed, 14 insertions(+), 0 deletions(-) --------------040700040300000504090809 Content-Type: text/plain; x-mac-type="54455854"; x-mac-creator="0"; name="spinlocks.txt.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="spinlocks.txt.patch" diff --git a/Documentation/spinlocks.txt b/Documentation/spinlocks.txt index 619699d..c112052 100644 --- a/Documentation/spinlocks.txt +++ b/Documentation/spinlocks.txt @@ -233,4 +233,18 @@ indeed), while write-locks need to protect themselves against interrupts. Linus +---- + +The implications of spin_locks on memory are further described in: + + Documentation/memory-barriers.txt + (5) LOCK operations. + (6) UNLOCK operations. + +---- + +We are working hard to remove reader-writer spinlocks (rw_lock) from the +network stack, so please don't add a new one. Instead, see: + + Documentation/RCU/rcu.txt -- 1.6.3.3 --------------040700040300000504090809--