netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Kieran Mansley <kmansley@solarflare.com>
Cc: Keir Fraser <keir@xensource.com>,
	muli@il.ibm.com, netdev@vger.kernel.org,
	xen-devel@lists.xensource.com, herbert@gondor.apana.org.au
Subject: Re: [Xen-devel] Re: [PATCH 3/4] [Net] Support Xen accelerated network plugin modules
Date: Tue, 22 May 2007 08:05:12 -0700	[thread overview]
Message-ID: <20070522080512.6c9528a1@freepuppy> (raw)
In-Reply-To: <1179837868.28562.22.camel@moonstone.uk.level5networks.com>

On Tue, 22 May 2007 13:44:28 +0100
Kieran Mansley <kmansley@solarflare.com> wrote:

> On Tue, 2007-05-22 at 08:48 +0100, Keir Fraser wrote:
> > 
> > 
> > On 22/5/07 08:28, "Kieran Mansley" <kmansley@solarflare.com> wrote:
> > 
> > > On Tue, 2007-05-22 at 08:15 +0100, Kieran Mansley wrote:
> > >> RCU on its own wouldn't
> > >> prevent the accelerated plugin being unloaded while netfront was using
> > >> one of the hooks.
> > > 
> > > Hmm, actually I think it could be used to do that.  I'll take a look.
> > 
> > Eagerly zap the function pointers, then wait one RCU period so every CPU
> > goes through a quiescent point before unloading the module?
> > 
> >  -- Keir
> 
> Am I right in thinking that if one of the functions that was protected
> by RCU was to block, that would be a bad thing?  Clearly the data path
> hooks can't/don't block, but I'm not sure it's so obvious for things
> like probing a new device. 
> 
> Kieran
> 

The same thing is already done to handle network protocols already.
RCU is used for the object handle (including function pointers).
You need to use:
  * put rcu structure in accelerator list member
    and initialize it to the callback
  * on addition increase refcount
on deletion
  * call list_del_rcu() on removal
  * in rcu callback you do last step
	like drop module refcount and free.

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

  parent reply	other threads:[~2007-05-22 15:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 13:16 [PATCH 3/4] [Net] Support Xen accelerated network plugin modules Kieran Mansley
2007-05-21 17:50 ` Stephen Hemminger
2007-05-22  7:00   ` Kieran Mansley
2007-05-21 17:52 ` Stephen Hemminger
2007-05-22  7:15   ` Kieran Mansley
2007-05-22  7:28     ` Kieran Mansley
2007-05-22  7:48       ` [Xen-devel] " Keir Fraser
2007-05-22  7:59         ` Kieran Mansley
2007-05-22 12:44         ` Kieran Mansley
2007-05-22 14:07           ` Keir Fraser
2007-05-22 14:20             ` Kieran Mansley
2007-05-22 15:05           ` Stephen Hemminger [this message]
2007-05-22 16:06             ` Kieran Mansley
2007-05-25  6:53     ` Andi Kleen
2007-05-21 17:54 ` 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=20070522080512.6c9528a1@freepuppy \
    --to=shemminger@linux-foundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=keir@xensource.com \
    --cc=kmansley@solarflare.com \
    --cc=muli@il.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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).