| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH 3/4] [Net] Support Xen accelerated network pl
On Tue, 2007-05-22 at 08:05 -0700, Stephen Hemminger wrote:
> 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.
Apologies for coming back to this, but I want to make sure this is going
to work before I write the code.
The current scheme uses a spin lock to protect the list and a reference
count for each item on that list. This reference count is initialised
to 1 when the accelerator module is loaded, incremented before each call
into the accelerator, decremented after it, and decremented when the
module's exit function is called as a result of rmmod being called on
the module. rmmod is then blocked. When the ref count reaches zero the
function pointers are set to NULL, resulting in no more calls into the
accelerator module, and the rmmod is unblocked. The accelerator now
exits safely.
The critical bits I don't understand about your suggested scheme are:
i) how deletion/list_del_rcu() is triggered (see below);
ii) how it prevents the accelerated module being unloaded in the middle
of call into that module.
I assume you're suggesting using the module use count to solve (ii), but
this essentially causes (i): if we increase the module use count for
each interface using the accelerator we can never unload the module
because there's no mechanism to request that an interface stop being
accelerated (and so decrease the ref count).
If you're suggesting using RCU to protect against the hooks being
modified during a call into them, that's only allowed if the protected
region doesn't block, and I'm not convinced that the protected regions
here (the calls into the accelerator module) will never block.
Apologies again if I've misinterpreted your suggestion,
Kieran
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home