[ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.

This is necessary because, in a multicore environment, a race between uverbs async handler and destroy QP could occur. Signed-off-by: Stefan Roscher stefan.roscher at de.ibm.com --- We are not sure if this should be fixed in the driver or in uverbs itself. Roland, what's your opinion about this?

Re: [ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.

We are not sure if this should be fixed in the driver or in uverbs itself. Roland, what's your opinion about this? Would be nice to be able to fix it in uverbs but I don't see how. In particular a kernel consumer has to have the same guarantee that no async events will come in after destroy

Re: [ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.

On Wednesday 07 May 2008 17:32:03 Roland Dreier wrote: We are not sure if this should be fixed in the driver or in uverbs itself. Roland, what's your opinion about this? Would be nice to be able to fix it in uverbs but I don't see how. In particular a kernel consumer has to have the

Re: [ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.

I agree, that's why I posted the driver fix first. Glad we agree :) I thought about it a little more and really convinced myself that there is no good way for generic code to handle this race. So, will you apply it next? Yes, will apply it shortly. - R.

[ewg] [PATCH ofed-1.3.1] IB/ipath - update ipath driver to include fixes being sent to 2.6.26

This patch includes a number of fixes for OFED-1.3.1 which have been or soon will be submitted to 2.6.26. They can be pulled or accessed at: git://git.openfabrics.org/~ralphc/linux-2.6/.git commit 21f5def290d9840ee16973d00c12aad4cf542bb5 Author: Ralph Campbell (QLogic) [EMAIL PROTECTED] Date:

[ewg] Interesting Herbal Offers

While browsing our extensive product line we ensure your digital security. www railweather com We ensure your full satisfaction in the utmost safest fashion. ___ ewg mailing list ewg@lists.openfabrics.org

Re: [ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.

So I applied this, but thinking about it further, do you (theoretically at least) have the same problem with CQ and SRQ async events? - R. ___ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg

[ewg] Re: [ofa-general] Re: [PATCH] Request For Comments:

I'm just trying to define the scope of the issue here... so is there any conceivable real-life situation where neither a 0B read nor a 0B write would work, and the connection setup will have to use a 0B send? i'm not sure what you mean by real-life. For the rnics we have: nes -

[ewg] Re: [ofa-general] Re: [PATCH] Request For Comments:

Sean Hefty wrote: nes - requires 0b write cxgb3 - requires 0b read amso1100 - won't work in p2p mode I'm assuming by requires that you, uhm, mean requires, and nes couldn't do 0b reads, or cxgb3 0b writes. Well, I'm not sure about nes. But cxgb3 cannot deal with receiving a 0B write