From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next-2.6] net: sk_dst_cache RCUification
Date: Wed, 14 Apr 2010 07:35:25 +0200
Message-ID: <1271223325.16881.600.camel@edumazet-laptop>
References: <1270803809.2623.69.camel@edumazet-laptop>
	 <20100413.015232.67916764.davem@davemloft.net>
	 <1271199845.16881.586.camel@edumazet-laptop>
	 <20100413.161153.135265420.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: netdev@vger.kernel.org, paulmck@linux.vnet.ibm.com
To: David Miller <davem@davemloft.net>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-bw0-f219.google.com ([209.85.218.219]:43386 "EHLO
	mail-bw0-f219.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752604Ab0DNFmW (ORCPT
	<rfc822;netdev@vger.kernel.org>); Wed, 14 Apr 2010 01:42:22 -0400
Received: by bwz19 with SMTP id 19so3112bwz.21
        for <netdev@vger.kernel.org>; Tue, 13 Apr 2010 22:42:20 -0700 (PDT)
In-Reply-To: <20100413.161153.135265420.davem@davemloft.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

Le mardi 13 avril 2010 =C3=A0 16:11 -0700, David Miller a =C3=A9crit :
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Wed, 14 Apr 2010 01:04:05 +0200
>=20
> > Instead of using rcu on whole "struct socket", my plan is to use a =
small
> > structure :
> >=20
> > struct wait_queue_head_rcu {
> > 	wait_queue_head_t wait;
> > 	struct rcu_head	  rcu;
> > } ____cacheline_aligned_in_smp;
> >=20
> > and make sk->sk_sleep points to this 'wait' field.
>=20
> So you're relying upon the fact that in the non-FASYNC case
> the struct socket's wait queue is never actually used?

Yes, for the first phase of my work, by asynch handling might be RCUfie=
d
too in a second phase :)