From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964798AbbJHPiO (ORCPT ); Thu, 8 Oct 2015 11:38:14 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:35523 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933685AbbJHPiN (ORCPT ); Thu, 8 Oct 2015 11:38:13 -0400 Date: Thu, 8 Oct 2015 14:03:28 +0100 From: Greg Kroah-Hartman To: Vlad Zolotarov Cc: Stephen Hemminger , Linux Kernel , bruce.richardson@intel.com, hjk@hansjkoch.de, corbet@lwn.net, avi@cloudius-systems.com, gleb@cloudius-systems.com, alexander.duyck@gmail.com, mst@redhat.com Subject: Re: [PATCH v5 1/4] uio: add ioctl support Message-ID: <20151008130328.GA31866@kroah.com> References: <1444151859-10217-1-git-send-email-vladz@cloudius-systems.com> <1444151859-10217-2-git-send-email-vladz@cloudius-systems.com> <20151007084627.GA4270@kroah.com> <5614DDE5.1050100@cloudius-systems.com> <20151007172112.GC9702@kroah.com> <5615562A.1070105@cloudius-systems.com> <56156BEA.4050809@cloudius-systems.com> <56166485.9090808@cloudius-systems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56166485.9090808@cloudius-systems.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 08, 2015 at 03:41:41PM +0300, Vlad Zolotarov wrote: > > > On 10/07/15 22:51, Stephen Hemminger wrote: > > > >I was thinking of not naming it uio at all > > > > U mean doing something completely orthogonal to UIO? And how did u thing to > access bars? With UIO or implement this functionality in the new configfs > too? > If yes - then it will essentially be UIO with MSI-X support, won't it? ;) > It'll also be the third user-space drivers infrastructure and I'm not sure > there is enough motivation add it. > Note that "some on this thread" are claiming that even two is too many... ;) Let's wait to see what happens here, I talked to Stephen and I think that a non-UIO driver might be the correct solution here. At the very least, the proposed patches are not acceptable, so it can't be any worse :) greg k-h