From: Octavian Purdila <opurdila@ixiacom.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [RFC PATCH] llc: convert the socket list to RCU locking (was Re: [PATCH 3/4] llc: use a device based hash table to speed up multicast delivery)
Date: Wed, 9 Dec 2009 22:36:06 +0200 [thread overview]
Message-ID: <200912092236.06298.opurdila@ixiacom.com> (raw)
In-Reply-To: <4B20064C.7070301@gmail.com>
On Wednesday 09 December 2009 22:19:24 you wrote:
> > + rcu_read_lock();
> > + sk_nulls_for_each_rcu(rc, node, &sap->sk_list) {
> > + if (llc_estab_match(sap, daddr, laddr, rc)) {
> > + /* Extra checks required by SLAB_DESTROY_BY_RCU */
> > + if (unlikely(!atomic_inc_not_zero(&rc->sk_refcnt)))
> > + continue;
>
> Hmm, this wont work in fact, because if we have several llc_sap allocated
> on machine, we have no guarantee a freed socket wont be reused and
> inserted in another llc_sap list.
>
> So before calling llc_estab_match() (and/or llc_listener_match()) you
> should check if 'rc' really belong to current sap.
>
> If not, you must restart the lookup (you hit a socket that was moved to
> another sap)
>
Right !
>>
>> One doubt before pasting the code: In slab.h comment and in udp.c I see the
lookup is restarted if an improper object is returned. Is that really
required?
>>
>
>
>Its needed only if you convert to a hash table (more than one chain),
>and I guess you definitly want a fanout of your XXXX items ?
>
>Check Documentation/RCU/rculist_nulls.txt for details :)
And of course I'll still want to add the hash table ;) I was just trying to
get my head around something simpler first.
I think I have everything (in my head :) ) that I need now to come back with
a v2 llc patch set now. Thanks for your help !
next prev parent reply other threads:[~2009-12-09 20:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 22:31 [PATCH 0/4] llc enhancements Octavian Purdila
2009-12-03 22:31 ` [PATCH 1/4] llc: use dev_hard_header Octavian Purdila
2009-12-03 22:31 ` [PATCH 2/4] llc: add support for LLC_OPT_PKTINFO Octavian Purdila
2009-12-03 22:31 ` [PATCH 3/4] llc: use a device based hash table to speed up multicast delivery Octavian Purdila
2009-12-03 22:59 ` Eric Dumazet
2009-12-03 23:30 ` Octavian Purdila
2009-12-03 23:52 ` Eric Dumazet
2009-12-04 0:15 ` Octavian Purdila
2009-12-04 0:28 ` Eric Dumazet
2009-12-08 21:10 ` [RFC PATCH] llc: convert the socket list to RCU locking (was Re: [PATCH 3/4] llc: use a device based hash table to speed up multicast delivery) Octavian Purdila
2009-12-08 21:26 ` Eric Dumazet
2009-12-09 20:19 ` Eric Dumazet
2009-12-09 20:36 ` Octavian Purdila [this message]
2009-12-09 21:49 ` Octavian Purdila
2009-12-09 22:34 ` Eric Dumazet
2009-12-09 20:52 ` Jarek Poplawski
2009-12-03 23:25 ` [PATCH 3/4] llc: use a device based hash table to speed up multicast delivery Stephen Hemminger
2009-12-03 23:53 ` Octavian Purdila
2009-12-04 0:37 ` Stephen Hemminger
2009-12-03 22:31 ` [PATCH 4/4] llc: replace the socket list with a local address based hash Octavian Purdila
2009-12-03 23:55 ` [PATCH 0/4] llc enhancements David Miller
2009-12-04 0:20 ` Octavian Purdila
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=200912092236.06298.opurdila@ixiacom.com \
--to=opurdila@ixiacom.com \
--cc=acme@ghostprotocols.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).