[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110217.145333.232751283.davem@davemloft.net>
Date: Thu, 17 Feb 2011 14:53:33 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: cmetcalf@...era.com
Cc: xiyou.wangcong@...il.com, cypher.w@...il.com,
linux-kernel@...r.kernel.org, eric.dumazet@...il.com,
netdev@...r.kernel.org
Subject: Re: IGMP and rwlock: Dead ocurred again on TILEPro
From: Chris Metcalf <cmetcalf@...era.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?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists