[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1828884A29C6694DAF28B7E6B8A82373AB04235E@ORSMSX109.amr.corp.intel.com>
Date: Fri, 15 Apr 2016 17:46:45 +0000
From: "Hefty, Sean" <sean.hefty@...el.com>
To: Christoph Hellwig <hch@...radead.org>,
Leon Romanovsky <leon@...n.nu>
CC: "Weiny, Ira" <ira.weiny@...el.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
"Dalessandro, Dennis" <dennis.dalessandro@...el.com>,
"dledford@...hat.com" <dledford@...hat.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/7] IB/hfi1: Remove write() and use ioctl() for user
access
> > Great, did you show it to other RDMA stakeholders except Intel?
> > I saw nothing posted on ML or proposed for initial discussion, which
> > will be held in the next week or two.
>
> I fear it's kfabrics, which is an entirely crackpot idea and a total
> non-starter, but for some reason Intel and their buddies keep wasting
> time on it.
There were discussions between several developers from multiple companies around moving away from using writev. That's it. Making random accusations and throwing crap over the wall does nothing to improve the community or instill trust.
Powered by blists - more mailing lists