From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Kieran Mansley <kmansley@solarflare.com>
Cc: 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: Mon, 21 May 2007 10:54:45 -0700 [thread overview]
Message-ID: <20070521105445.60d69f2c@freepuppy> (raw)
In-Reply-To: <1179494208.14376.10.camel@moonstone.uk.level5networks.com>
O
> +
> +/*
> + * Macro to call one of the accelerator's function hooks. The use
> + * count for the accelerator's hooks is incremented for the duration
> + * of the call to prevent the accelerator being able to modify the
> + * hooks in the middle (by, for example, unloading)
> + */
> +#define netfront_call_accelerator_hook(_np, _hook, _args...)
> \
> + do {
> \
> + if ( (_np)->accel_vif_state.hooks ) {
> \
> + unsigned flags;
> \
> + spin_lock_irqsave(&accelerators_lock, flags);
> \
> + ++(_np)->accelerator->hooks_usecount;
> \
> + spin_unlock_irqrestore(&accelerators_lock,
> flags); \
> + if ( (_np)->accel_vif_state.hooks )
> \
> + (_np)->accel_vif_state.hooks->_hook
> (_args); \
> + spin_lock_irqsave(&accelerators_lock, flags);
> \
> + if ( (--(_np)->accelerator->hooks_usecount) ==
> 0 ) \
> + accelerator_remove_hooks((_np)-
> >accelerator); \
> + spin_unlock_irqrestore(&accelerators_lock,
> flags); \
> + }
> \
> + } while(0)
Gag, why a macro... See earlier comments about suing RCU and eliminating
the refcount and locking overhead.
--
Stephen Hemminger <shemminger@linux-foundation.org>
prev parent reply other threads:[~2007-05-21 17: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
2007-05-21 17:54 ` Stephen Hemminger [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=20070521105445.60d69f2c@freepuppy \
--to=shemminger@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--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 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.