From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [net-next PATCH V2 8/9] net: frag queue locking per hash bucket Date: Thu, 29 Nov 2012 09:08:40 -0800 Message-ID: <1354208920.14302.1907.camel@edumazet-glaptop> References: <20121129161019.17754.29670.stgit@dragon> <20121129161512.17754.93933.stgit@dragon> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , Florian Westphal , netdev@vger.kernel.org, Pablo Neira Ayuso , Thomas Graf , Cong Wang , Patrick McHardy , "Paul E. McKenney" , Herbert Xu To: Jesper Dangaard Brouer Return-path: Received: from mail-pa0-f46.google.com ([209.85.220.46]:46410 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751734Ab2K2RIp (ORCPT ); Thu, 29 Nov 2012 12:08:45 -0500 Received: by mail-pa0-f46.google.com with SMTP id bh2so7758810pad.19 for ; Thu, 29 Nov 2012 09:08:45 -0800 (PST) In-Reply-To: <20121129161512.17754.93933.stgit@dragon> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 2012-11-29 at 17:15 +0100, Jesper Dangaard Brouer wrote: > This patch implements per hash bucket locking for the frag queue > hash. This removes two write locks, and the only remaining write > lock is for protecting hash rebuild. This essentially reduce the > readers-writer lock to a rebuild lock. So we still have this huge contention on the reader-writer lock cache line... I would just remove it. (And remove hash rebuild, or make it RCU compatible )