From: Roland Dreier <rdreier@cisco.com>
To: Stefan Roscher <ossrosch@linux.vnet.ibm.com>
Cc: LinuxPPC-Dev <linuxppc-dev@ozlabs.org>,
fenkes@de.ibm.com, LKML <linux-kernel@vger.kernel.org>,
raisch@de.ibm.com, OF-EWG <ewg@lists.openfabrics.org>
Subject: Re: [ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.
Date: Wed, 07 May 2008 08:32:03 -0700 [thread overview]
Message-ID: <adahcdaw2oc.fsf@cisco.com> (raw)
In-Reply-To: <200805071319.37164.ossrosch@linux.vnet.ibm.com> (Stefan Roscher's message of "Wed, 7 May 2008 13:19:35 +0200")
> 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 QP returns. And I don't see any
way generic code can provide a guarantee about what low-level driver
code may do internally.
WARNING: multiple messages have this Message-ID (diff)
From: Roland Dreier <rdreier@cisco.com>
To: Stefan Roscher <ossrosch@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"LinuxPPC-Dev" <linuxppc-dev@ozlabs.org>,
"OF-EWG" <ewg@lists.openfabrics.org>,
fenkes@de.ibm.com, raisch@de.ibm.com
Subject: Re: [ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.
Date: Wed, 07 May 2008 08:32:03 -0700 [thread overview]
Message-ID: <adahcdaw2oc.fsf@cisco.com> (raw)
In-Reply-To: <200805071319.37164.ossrosch@linux.vnet.ibm.com> (Stefan Roscher's message of "Wed, 7 May 2008 13:19:35 +0200")
> 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 QP returns. And I don't see any
way generic code can provide a guarantee about what low-level driver
code may do internally.
next prev parent reply other threads:[~2008-05-07 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 11:19 [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled Stefan Roscher
2008-05-07 11:19 ` Stefan Roscher
2008-05-07 15:32 ` Roland Dreier [this message]
2008-05-07 15:32 ` [ewg] " Roland Dreier
2008-05-07 16:00 ` Stefan Roscher
2008-05-07 16:00 ` Stefan Roscher
2008-05-07 18:02 ` Roland Dreier
2008-05-07 18:02 ` Roland Dreier
2008-05-07 19:18 ` Roland Dreier
2008-05-07 19:18 ` Roland Dreier
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=adahcdaw2oc.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ewg@lists.openfabrics.org \
--cc=fenkes@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ossrosch@linux.vnet.ibm.com \
--cc=raisch@de.ibm.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.