From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by dpdk.org (Postfix) with ESMTP id 700693989 for ; Wed, 5 Nov 2014 13:51:50 +0100 (CET) Received: by mail-wi0-f176.google.com with SMTP id h11so12318217wiw.9 for ; Wed, 05 Nov 2014 05:01:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=D4PJEjtDJT8emZSeVWUrg3GEvg1dvfpACUHT8NDNaAg=; b=lqcosrK0TpDZjr8w1la99CML3krNjQOA7UJJmr4+BkFFRdjGQavYf0SpgUTQmK8Dhr YR8dGLSk9x6Ah+s+FW3y5GtjK6dBEQ/dT02NBbYqoZ/B4ubQCP8KFU93E70/aPOT351I g9EKlBZig/sm8JgAWL1n3FYxfHvJEFonIuHBoxSoUfbxlB0RrDR/Qlakgcv7+vq+zYfd 7wFolAVFST37ZWv+0Y2QmlaaUX+nhggGfjNepujZGv/jz/dcfEAOkJG5kaREFwnYVFYt MNQ3Z/eJc2I8xSqdocIeK8Juknj/lHYsVyLxiXyirkF3EenBjqJvGZiVZTd915MN6Mr7 liIA== X-Gm-Message-State: ALoCoQn/m6m4v9GK7hOfJI7W82VOVU2+4HliyjOKsZyQa4bRRCalF9Vn5SMvyYA/I4Lv63QU9PxT X-Received: by 10.180.212.5 with SMTP id ng5mr18767335wic.50.1415192473291; Wed, 05 Nov 2014 05:01:13 -0800 (PST) Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by mx.google.com with ESMTPSA id cg15sm2041325wjb.34.2014.11.05.05.01.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Nov 2014 05:01:12 -0800 (PST) From: Thomas Monjalon To: danny.zhou@intel.com Date: Wed, 05 Nov 2014 14:00:53 +0100 Message-ID: <4163036.7ZLDrAu3iM@xps13> Organization: 6WIND User-Agent: KMail/4.14.2 (Linux/3.17.2-1-ARCH; KDE/4.14.2; x86_64; ; ) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C46444@IRSMSX102.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C42C29@IRSMSX102.ger.corp.intel.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA54C4620C@IRSMSX102.ger.corp.intel.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA54C46444@IRSMSX102.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org, john.r.fastabend@intel.com Subject: Re: [dpdk-dev] bifurcated driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2014 12:51:50 -0000 Hi Danny, 2014-10-31 17:36, O'driscoll, Tim: > Bifurcated Driver (Danny.Zhou@intel.com) Thanks for the presentation of bifurcated driver during the community call. I asked if you looked at ibverbs and you wanted a link to check. The kernel module is here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/infiniband/core The userspace library: http://git.kernel.org/cgit/libs/infiniband/libibverbs.git Extract from Kconfig: " config INFINIBAND_USER_ACCESS tristate "InfiniBand userspace access (verbs and CM)" select ANON_INODES ---help--- Userspace InfiniBand access support. This enables the kernel side of userspace verbs and the userspace communication manager (CM). This allows userspace processes to set up connections and directly access InfiniBand hardware for fast-path operations. You will also need libibverbs, libibcm and a hardware driver library from . " It seems to be close to the bifurcated driver needs. Not sure if it can solve the security issues if there is no dedicated MMU in the NIC. I feel we should sum up pros and cons of - igb_uio - uio_pci_generic - VFIO - ibverbs - bifurcated driver I suggest to consider these criterias: - upstream status - usable with kernel netdev - usable in a vm - usable for ethernet - hardware requirements - security protection - performance -- Thomas