From: Peter Zijlstra <peterz@infradead.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Cypher Wu <cypher.w@gmail.com>,
linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: Kernel rwlock design, Multicore and IGMP
Date: Sat, 13 Nov 2010 23:54:20 +0100 [thread overview]
Message-ID: <1289688860.2109.401.camel@laptop> (raw)
In-Reply-To: <20101112081945.GA5949@cr0.nay.redhat.com>
On Fri, 2010-11-12 at 16:19 +0800, Américo Wang wrote:
>
> Just for record, both Tile and X86 implement rwlock with a write-bias,
> this somewhat reduces the write-starvation problem.
x86 does no such thing.
next prev parent reply other threads:[~2010-11-13 22:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 13:49 Kernel rwlock design, Multicore and IGMP Cypher Wu
2010-11-11 15:23 ` Eric Dumazet
2010-11-11 15:32 ` Eric Dumazet
2010-11-12 3:32 ` Cypher Wu
2010-11-12 6:28 ` Américo Wang
2010-11-12 7:13 ` Américo Wang
2010-11-12 7:27 ` Eric Dumazet
2010-11-12 8:19 ` Américo Wang
2010-11-12 9:09 ` Yong Zhang
2010-11-12 9:18 ` Américo Wang
2010-11-12 11:06 ` Cypher Wu
2010-11-13 6:35 ` Américo Wang
2010-11-12 13:00 ` Yong Zhang
2010-11-13 6:28 ` Américo Wang
2010-11-12 9:22 ` Eric Dumazet
2010-11-12 9:33 ` Américo Wang
2010-11-12 13:34 ` [PATCH net-next-2.6] igmp: RCU conversion of in_dev->mc_list Eric Dumazet
2010-11-12 14:26 ` Eric Dumazet
2010-11-12 15:46 ` [PATCH net-next-2.6 V2] " Eric Dumazet
2010-11-12 21:19 ` David Miller
2010-11-13 6:44 ` Américo Wang
2010-11-13 22:54 ` Peter Zijlstra [this message]
2010-11-12 11:10 ` Kernel rwlock design, Multicore and IGMP Cypher Wu
2010-11-12 11:25 ` Eric Dumazet
2010-11-13 22:53 ` Peter Zijlstra
[not found] ` <ZXmP8hjgLHA.4648@exchange1.tad.internal.tilera.com>
2010-11-13 23:03 ` Chris Metcalf
2010-11-15 7:22 ` Cypher Wu
2010-11-15 11:18 ` Cypher Wu
2010-11-15 11:31 ` Eric Dumazet
2010-11-17 1:30 ` Cypher Wu
2010-11-17 4:43 ` Eric Dumazet
2010-11-15 14:18 ` [PATCH] arch/tile: fix rwlock so would-be write lockers don't block new readers Chris Metcalf
2010-11-15 14:52 ` Eric Dumazet
2010-11-15 15:10 ` Chris Metcalf
2010-11-22 5:39 ` Cypher Wu
2010-11-22 13:35 ` Chris Metcalf
2010-11-23 1:36 ` Cypher Wu
2010-11-23 21:02 ` Chris Metcalf
2010-11-24 2:53 ` Cypher Wu
2010-11-24 14:09 ` Chris Metcalf
2010-11-24 16:37 ` Cypher Wu
2010-11-13 22:52 ` Kernel rwlock design, Multicore and IGMP Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289688860.2109.401.camel@laptop \
--to=peterz@infradead.org \
--cc=cypher.w@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox