From: Leon Romanovsky <leonro@mellanox•com>
To: Or Gerlitz <gerlitz.or@gmail•com>
Cc: Ariel Almog <arielalmogworkemails@gmail•com>,
"linux-rdma@vger•kernel.org" <linux-rdma@vger•kernel.org>,
Linux Netdev List <netdev@vger•kernel.org>
Subject: Re: [RFC] RESEND - rdmatool - tool for RDMA users
Date: Wed, 18 Jan 2017 20:28:57 +0200 [thread overview]
Message-ID: <20170118182857.GG32481@mtr-leonro.local> (raw)
In-Reply-To: <CAJ3xEMiR1+NGghUZJ6aGq+=xTdOHU5Ph-BcPii5OUB8dT4Vq-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
On Wed, Jan 18, 2017 at 07:50:26PM +0200, Or Gerlitz wrote:
> On Wed, Jan 18, 2017 at 7:33 PM, Leon Romanovsky wrote:
> > On Wed, Jan 18, 2017 at 06:48:21PM +0200, Or Gerlitz wrote:
> >> On Wed, Jan 18, 2017 at 5:19 PM, Ariel Almog
> >> <arielalmogworkemails@gmail•com> wrote:
>
> >>> As of today, there is no single, simple, tool that allows monitoring
> >>> and configuration of RDMA stack.
>
> >> Before tool, what kernel UAPI you thought to use?
>
> > I'm aware of the following options:
> > 1) netlink
> > 2) RDMA ABI https://www.spinics.net/lists/linux-rdma/msg43960.html
> > 3) ioctl
> > 4) write/read
> >
> > The items 1 and 2 are preferred options and one of the main goals
> > for this RFC is to chose between them.
> >
> > For example, RDMA ABI has native support of querying and discovering
> > device capabilities via merge tree feature.
>
> To make it clear, when you wrote ABI in your initial email, I tend to
> think it was sort of unclear to the netdev crowd that you are talking
> on new UAPI which is now under the works for the IB subsystem, so with
> my netdev community member hat, I got confused... anyway
You are right, I missed it in my review for Ariel who wrote this RFC
and sent this RFC.
Thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-18 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 15:19 [RFC] RESEND - rdmatool - tool for RDMA users Ariel Almog
[not found] ` <CABvr3-GZQs51Sn3XagTsepsy3CHvx6P=GVJzefajbNt9jxz9Kg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-18 16:48 ` Or Gerlitz
2017-01-18 17:33 ` Leon Romanovsky
2017-01-18 17:50 ` Or Gerlitz
2017-01-18 18:28 ` Leon Romanovsky [this message]
2017-01-18 18:31 ` Jason Gunthorpe
2017-01-18 21:45 ` Bart Van Assche
[not found] ` <5f90fd26-e7bf-bb2a-01f2-6b166f2265e9-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2017-01-19 6:33 ` Leon Romanovsky
[not found] ` <20170119063326.GJ32481-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-19 18:03 ` Jason Gunthorpe
2017-01-19 19:12 ` Leon Romanovsky
2017-01-19 22:06 ` Bart Van Assche
2017-01-19 22:16 ` Jason Gunthorpe
[not found] ` <20170119180308.GD8109-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-31 11:38 ` Ariel Almog
2017-01-19 6:04 ` Leon Romanovsky
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=20170118182857.GG32481@mtr-leonro.local \
--to=leonro@mellanox$(echo .)com \
--cc=arielalmogworkemails@gmail$(echo .)com \
--cc=gerlitz.or@gmail$(echo .)com \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox