From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: neighbour table RCU
Date: Mon, 31 Aug 2009 15:04:53 -0700 [thread overview]
Message-ID: <20090831150453.3437a65c@nehalam> (raw)
Looking at the neighbour table, it should be possible to get
rid of the two reader/writer locks. The hash table lock is pretty
amenable to RCU, but the dynamic resizing makes it non-trivial.
Thinking of using a combination of RCU and sequence counts so that the
reader would just rescan if resize was in progress.
The reader/writer lock on the neighbour entry is more of a problem.
Probably would be simpler/faster to change it into a spinlock and
be done with it.
The reader/writer lock is also used for the proxy list hash table,
but that can just be a simple spinlock.
--
next reply other threads:[~2009-08-31 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 22:04 Stephen Hemminger [this message]
2009-09-01 6:50 ` neighbour table RCU Eric Dumazet
2009-09-01 15:55 ` Octavian Purdila
2009-09-01 16:14 ` Eric Dumazet
2009-09-01 16:56 ` Octavian Purdila
2009-09-01 16:23 ` Stephen Hemminger
2009-09-01 15:59 ` Stephen Hemminger
2009-09-01 16:13 ` Eric Dumazet
2009-09-01 21:24 ` Stephen Hemminger
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=20090831150453.3437a65c@nehalam \
--to=shemminger@vyatta.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.