From: Octavian Purdila <opurdila@ixiacom.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] sk_nulls_next_rcu
Date: Fri, 4 Dec 2009 00:47:02 +0200 [thread overview]
Message-ID: <200912040047.02539.opurdila@ixiacom.com> (raw)
In-Reply-To: <20091201005929.GB21463@ghostprotocols.net>
On Tuesday 01 December 2009 02:59:29 you wrote:
> Em Tue, Dec 01, 2009 at 02:19:29AM +0200, Octavian Purdila escreveu:
> > I am trying to convert the LLC code to RCU, and it appears that for proc
> > support a sk_nulls_next_rcu would be required.
>
> I find it amusing, and give you a carte blanche on that! :-)
>
:-) Its just an exercise for me to understand RCU, but its harder than I
originally thought and I did give up trying to finish it in the first batch of
LLC patches I've just sent.
prev parent reply other threads:[~2009-12-03 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 0:19 [RFC] sk_nulls_next_rcu Octavian Purdila
2009-12-01 0:24 ` David Miller
2009-12-01 0:32 ` Octavian Purdila
2009-12-01 3:54 ` Eric Dumazet
2009-12-01 0:59 ` Arnaldo Carvalho de Melo
2009-12-03 22:47 ` Octavian Purdila [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=200912040047.02539.opurdila@ixiacom.com \
--to=opurdila@ixiacom.com \
--cc=acme@ghostprotocols.net \
--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).