From: David Miller <davem@davemloft.net>
To: cmetcalf@tilera.com
Cc: xiyou.wangcong@gmail.com, cypher.w@gmail.com,
linux-kernel@vger.kernel.org, eric.dumazet@gmail.com,
netdev@vger.kernel.org
Subject: Re: IGMP and rwlock: Dead ocurred again on TILEPro
Date: Thu, 17 Feb 2011 14:53:33 -0800 (PST) [thread overview]
Message-ID: <20110217.145333.232751283.davem@davemloft.net> (raw)
In-Reply-To: <4D5DA60A.8080201@tilera.com>
From: Chris Metcalf <cmetcalf@tilera.com>
Date: Thu, 17 Feb 2011 17:49:46 -0500
> The fix is to disable interrupts for the arch_read_lock family of methods.
How does that help handle the race when it happens between different
cpus, instead of between IRQ and non-IRQ context on the same CPU?
Why don't you just use the generic spinlock based rwlock code on Tile,
since that is all that your atomic instructions can handle
sufficiently?
next prev parent reply other threads:[~2011-02-17 22:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 3:39 Fwd: IGMP and rwlock: Dead ocurred again on TILEPro Cypher Wu
2011-02-17 4:49 ` Américo Wang
2011-02-17 5:04 ` Cypher Wu
2011-02-17 5:42 ` Américo Wang
2011-02-17 5:46 ` David Miller
2011-02-17 6:39 ` Eric Dumazet
2011-02-17 22:49 ` Chris Metcalf
2011-02-17 22:53 ` David Miller [this message]
2011-02-17 23:04 ` Chris Metcalf
2011-02-17 23:11 ` David Miller
2011-02-17 23:18 ` Chris Metcalf
2011-02-18 3:16 ` Cypher Wu
2011-02-18 3:19 ` Cypher Wu
2011-02-18 7:08 ` Cypher Wu
2011-02-18 21:51 ` Chris Metcalf
2011-02-19 4:07 ` Cypher Wu
2011-02-20 13:33 ` Chris Metcalf
2011-03-01 18:30 ` [PATCH] arch/tile: fix deadlock bugs in rwlock implementation Chris Metcalf
2011-02-17 6:42 ` Fwd: IGMP and rwlock: Dead ocurred again on TILEPro Cypher Wu
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=20110217.145333.232751283.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cmetcalf@tilera.com \
--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;
as well as URLs for NNTP newsgroup(s).