All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Adit Ranadive <aditr@vmware.com>
Cc: "dledford@redhat.com" <dledford@redhat.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Bryan Tan <bryantan@vmware.com>,
	Pv-drivers <Pv-drivers@vmware.com>
Subject: Re: [PATCH for-next v1] RDMA/vmw_pvrdma: Use resource ids from physical device if available
Date: Tue, 15 Oct 2019 14:06:13 -0300	[thread overview]
Message-ID: <20191015170613.GC5444@ziepe.ca> (raw)
In-Reply-To: <8F02F753-B71A-4F73-83D8-D6224D6C4F6B@vmware.com>

On Sat, Oct 12, 2019 at 07:03:55AM +0000, Adit Ranadive wrote:
> On 10/8/19, 11:15 AM, "Jason Gunthorpe" <jgg@ziepe.ca> wrote:
> > 
> > On Thu, Sep 19, 2019 at 08:24:56PM +0000, Adit Ranadive wrote:
> > 
> > >  
> > > +	if (!qp->is_kernel) {
> > > +		if (ucmd.flags == PVRDMA_USER_QP_CREATE_USE_RESP) {
> > 
> > Why does this flag exist? Don't old userspaces pass in a 0 length?
> > Just use the length to signal new userspace?
> 
> I did have that in an earlier version but we decided it to make it more
> explicit. It would be easier to add another flag later on if required
> than to check the length (which might be same).

You should add a flag if either the length or detecting value == 0 is
not sufficient to detect the new support. No reason to add things
until this situation comes up

Jason

  reply	other threads:[~2019-10-15 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 20:24 [PATCH for-next v1] RDMA/vmw_pvrdma: Use resource ids from physical device if available Adit Ranadive
2019-10-08 18:15 ` Jason Gunthorpe
2019-10-12  7:03   ` Adit Ranadive
2019-10-15 17:06     ` Jason Gunthorpe [this message]
2019-10-15 17:16       ` Adit Ranadive

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=20191015170613.GC5444@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=Pv-drivers@vmware.com \
    --cc=aditr@vmware.com \
    --cc=bryantan@vmware.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    /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.