Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751319AbcDORqt (ORCPT <rfc822;w@1wt.eu>);
	Fri, 15 Apr 2016 13:46:49 -0400
Received: from mga01.intel.com ([192.55.52.88]:46538 "EHLO mga01.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750709AbcDORqr convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 15 Apr 2016 13:46:47 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.24,488,1455004800"; 
   d="scan'208";a="955852196"
From: "Hefty, Sean" <sean.hefty@intel.com>
To: Christoph Hellwig <hch@infradead.org>, Leon Romanovsky <leon@leon.nu>
CC: "Weiny, Ira" <ira.weiny@intel.com>,
        Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
        "Dalessandro, Dennis" <dennis.dalessandro@intel.com>,
        "dledford@redhat.com" <dledford@redhat.com>,
        "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
        "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
        "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
        "viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/7] IB/hfi1: Remove write() and use ioctl() for user
 access
Thread-Topic: [PATCH 0/7] IB/hfi1: Remove write() and use ioctl() for user
 access
Thread-Index: AQHRlmTHh1wCfXBsAEC5Q4QXCcB1gJ+KIsIAgAARhICAAKs/AIAAzcWAgAAUToCAAAD2gP//jMtg
Date: Fri, 15 Apr 2016 17:46:45 +0000
Message-ID: <1828884A29C6694DAF28B7E6B8A82373AB04235E@ORSMSX109.amr.corp.intel.com>
References: <20160414153727.6387.96381.stgit@scvm10.sc.intel.com>
 <20160414164550.GC6247@obsidianresearch.com>
 <20160414174830.GA11641@rhel.sc.intel.com> <20160415040126.GB10689@leon.nu>
 <20160415161754.GA21549@rhel> <20160415173035.GC10689@leon.nu>
 <20160415173401.GA10868@infradead.org>
In-Reply-To: <20160415173401.GA10868@infradead.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZmU3Yjc2ZjItNDFhMC00NzhhLTkwMjctNmRmZDkxMDZiOTg3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InNESDh1TFBmZ2NmaHRxbjV1RzVjY2psTzJMXC9qcjZwNG9ma2w0cUxqaXJBPSJ9
x-ctpclassification: CTP_IC
x-originating-ip: [10.22.254.139]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 583
Lines: 9

> > 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.