All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Kieran Mansley <kmansley@solarflare.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	xen-devel@lists.xensource.com, netdev@vger.kernel.org,
	muli@il.ibm.com, herbert@gondor.apana.org.au
Subject: Re: [PATCH 3/4] [Net] Support Xen accelerated network plugin modules
Date: 25 May 2007 08:53:12 +0200	[thread overview]
Message-ID: <p73k5uxcs2v.fsf@bingen.suse.de> (raw)
In-Reply-To: <1179818108.4145.18.camel@moonstone.uk.level5networks.com>

Kieran Mansley <kmansley@solarflare.com> writes:

> RCU on its own wouldn't
> prevent the accelerated plugin being unloaded while netfront was using
> one of the hooks. 

Note that module unload does always does a stop_machine() which is much 
stronger than normal RCU. As long as you don't sleep and cannot be preemptable
it should be always safe.

-Andi

  parent reply	other threads:[~2007-05-25  5:56 UTC|newest]

Thread overview: 17+ 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:48         ` 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:07             ` Keir Fraser
2007-05-22 14:20             ` Kieran Mansley
2007-05-22 15:05           ` Stephen Hemminger
2007-05-22 16:06             ` Kieran Mansley
2007-05-25  6:53     ` Andi Kleen [this message]
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=p73k5uxcs2v.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kmansley@solarflare.com \
    --cc=muli@il.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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 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.