[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160916193102.GB28859@obsidianresearch.com>
Date: Fri, 16 Sep 2016 13:31:03 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Knut Omang <knut.omang@...cle.com>
Cc: Doug Ledford <dledford@...hat.com>, linux-rdma@...r.kernel.org,
linux-kernel@...r.kernel.org, Sean Hefty <sean.hefty@...el.com>,
Hal Rosenstock <hal.rosenstock@...il.com>,
Matan Barak <matanb@...lanox.com>,
Sagi Grimberg <sagi@...mberg.me>,
Leon Romanovsky <leonro@...lanox.com>,
Yishai Hadas <yishaih@...lanox.com>,
Majd Dibbiny <majd@...lanox.com>,
Eran Ben Elisha <eranbe@...lanox.com>,
Or Gerlitz <ogerlitz@...lanox.com>
Subject: Re: [PATCH v2 8/8] ib_uverbs: Support for kernel implementation of
XRC
On Fri, Sep 16, 2016 at 08:31:19PM +0200, Knut Omang wrote:
> +++ b/include/uapi/rdma/ib_user_verbs.h
> @@ -725,6 +725,8 @@ struct ib_uverbs_send_wr {
> __u32 reserved;
> } ud;
> } wr;
> + __u32 xrc_remote_srq_num;
> + __u32 reserved;
> };
You still need to discuss why this is OK...
Are you doing all this just to be able to use the existing post_send user
space path in the common code? Is there a kernel XRC user planned?
Another approach would be to implement post_send in your driver and
not rely on this common code path.
Jason
Powered by blists - more mailing lists