[openib-general] [PATCH] kDAPL: cleanup dat/ a bit more

Caitlin Bestler caitlin.bestler at gmail.com
Fri Jun 3 04:30:51 PDT 2005


The appropriate plafce to add that would be as an unafilliated asynchronous
event reported via the async evd.

The next question is to define what if any handshake is desired.
My guess that the consumer would acknowledge this by closing
the RNIC, and that there would be some sort of deadline for doing
so (much like a shutdown, you have so long to clean up, after that
-- well you were warned).

That is a simple extension to the DAT API that nobody has
found urgent enough yet to propose, but it fits within the 
general approach well. Why don't you propose such an
extension? You could even just create it and not wait
for a response, if the proposal is reasonable it will
naturally be merged back into the official DAT API.

On 6/2/05, Itamar Rabenstein <itamar at mellanox.co.il> wrote:
> Hi ,
> 
> I am not an expert to pci hot plug but as far as know we currently dont have
> away in kdapl
> to inform the consumer of kdapl that a provider is going to be unloaded.
> pci hot plug should enable any low level driver (openib) to inform high
> level driver(kdapl)
> that the devide is going down.
> 
> In openib gen2 this is doen with Ccall back remove_one().
> 
> how it is doen in current kdapl ?
> how the consumer who opened IA will know that this card is going down?
> 
> Itamar
> 
=



More information about the general mailing list