From: "David S. Miller" <davem@redhat.com>
To: hadi@shell.cyberus.ca
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2.5.69] Network packet type using RCU
Date: Mon, 19 May 2003 00:22:19 -0700 (PDT) [thread overview]
Message-ID: <20030519.002219.02298937.davem@redhat.com> (raw)
In-Reply-To: <20030514072006.D23367@shell.cyberus.ca>
From: Jamal Hadi <hadi@shell.cyberus.ca>
Date: Wed, 14 May 2003 07:23:32 -0400 (EDT)
Apologies i was offline for a bit so dont know the history here.
I see a lot of move to rcu. There are benefits to using RCU in certain
cases (example occasional list edit with a lot more reads). Why does
there seem to be a massive migration it seems to RCU? Something wrong
with the linked lists?
If you only need one of two synchronization primitives, why
have two? :-)
prev parent reply other threads:[~2003-05-19 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 21:25 [PATCH 2.5.69] Network packet type using RCU Stephen Hemminger
2003-05-14 11:23 ` Jamal Hadi
2003-05-14 19:19 ` David S. Miller
2003-05-19 7:22 ` David S. Miller [this message]
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=20030519.002219.02298937.davem@redhat.com \
--to=davem@redhat.com \
--cc=hadi@shell.cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).