From: Jason Gunthorpe <jgunthorpe@obsidianresearch•com>
To: Bart Van Assche <Bart.VanAssche@sandisk•com>
Cc: "leon@kernel•org" <leon@kernel•org>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"arielalmogworkemails@gmail•com" <arielalmogworkemails@gmail•com>,
"linux-rdma@vger•kernel.org" <linux-rdma@vger•kernel.org>,
"gerlitz.or@gmail•com" <gerlitz.or@gmail•com>
Subject: Re: [RFC] RESEND - rdmatool - tool for RDMA users
Date: Thu, 19 Jan 2017 15:16:51 -0700 [thread overview]
Message-ID: <20170119221651.GA1656@obsidianresearch.com> (raw)
In-Reply-To: <1484863558.2634.7.camel@sandisk.com>
On Thu, Jan 19, 2017 at 10:06:12PM +0000, Bart Van Assche wrote:
> On Thu, 2017-01-19 at 11:03 -0700, Jason Gunthorpe wrote:
> > sysfs is unpopular because the 'one value per file' dogma is laregly
> > unsuitable for complex mulit-value atomic changes which are common in
> > netdev. You can force it to work, but it is pretty horrible..
> >
> > It is also very expensive if you want to shuttle a lot of data, eg I
> > could not see doing something like 'netstat' for IB through sysfs
>
> Since the RDMA sysfs ABI defines a user space ABI and since user space
> ABIs must be backwards compatible removing the existing sysfs ABI is
> not an option. We will need to evaluate on a case-by-case basis whether
> new functionality should use sysfs or whether another mechanism should
> be used.
Not talking about getting rid of it.
But if it makes sense to use netlink for the new stuff we should make
netlink self-consistent so a netlink user does not have to fall back
to sysfs for certain things.
Jason
next prev parent reply other threads:[~2017-01-19 22:17 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
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 [this message]
[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=20170119221651.GA1656@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch$(echo .)com \
--cc=Bart.VanAssche@sandisk$(echo .)com \
--cc=arielalmogworkemails@gmail$(echo .)com \
--cc=gerlitz.or@gmail$(echo .)com \
--cc=leon@kernel$(echo .)org \
--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