From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lukego@gmail.com>
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com
 [209.85.212.175]) by dpdk.org (Postfix) with ESMTP id 63D982A9
 for <dev@dpdk.org>; Mon, 24 Nov 2014 12:46:56 +0100 (CET)
Received: by mail-wi0-f175.google.com with SMTP id l15so5386614wiw.8
 for <dev@dpdk.org>; Mon, 24 Nov 2014 03:57:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=PEjzhiUord85Zz04hx5QZa4x6iFOeX6wLw2nraJNiEo=;
 b=fyxzcDkHyizhGTOOIoX1/SsLpZI5DoR4pMUk4DBPzlhiCTaCcZ8R0d80Qg8+iEzkv4
 AXcCOcsGCd3sJ1iLBR3B3fIXmryJOlCm/VGpaNM8ZISSQt8kYwyWw8a02Q8CbA2Hl2qg
 tR62+iFl6DCNeqOM6oOAOmdX6kdz37qWjy9V2dnSei+XauEnU/OcoZ9m4xMe9S8RoEhN
 8ujrqAiGMG1fxGzzs3p1fVpikrDB6ugyEKIUR3qshc2Uiq33OoRaj0uLUCtr9wRksC57
 /e+mRNrSq8Mz7mwaC8Ka+uu31k2PHoONNTWcC8UDOSjngZsk+LI98CA4ja68n9u2KfpK
 GKfw==
MIME-Version: 1.0
X-Received: by 10.194.48.116 with SMTP id k20mr33975963wjn.7.1416830264015;
 Mon, 24 Nov 2014 03:57:44 -0800 (PST)
Sender: lukego@gmail.com
Received: by 10.27.174.18 with HTTP; Mon, 24 Nov 2014 03:57:43 -0800 (PST)
In-Reply-To: <4163036.7ZLDrAu3iM@xps13>
References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C42C29@IRSMSX102.ger.corp.intel.com>
 <26FA93C7ED1EAA44AB77D62FBE1D27BA54C4620C@IRSMSX102.ger.corp.intel.com>
 <26FA93C7ED1EAA44AB77D62FBE1D27BA54C46444@IRSMSX102.ger.corp.intel.com>
 <4163036.7ZLDrAu3iM@xps13>
Date: Mon, 24 Nov 2014 12:57:43 +0100
X-Google-Sender-Auth: dzmMp-ZZb7QX0glla9f1eZgkrCI
Message-ID: <CAA2XHbffNC=KcwFrxkUADpXA7EFYxJYwq8tLzvr-H0aYVd1T9Q@mail.gmail.com>
From: Luke Gorrie <luke@snabb.co>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: "dev@dpdk.org" <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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Nov 2014 11:46:56 -0000

On 5 November 2014 at 14:00, Thomas Monjalon <thomas.monjalon@6wind.com>
wrote:

> 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 am also curious about the pros and cons of the bifurcated driver compared
with SR-IOV.

What are the practical differences between running a bifurcated driver vs.
running SR-IOV mode where the kernel owns the PF and userspace applications
own the VFs?

Specifically, could I run the ixgbe driver in the kernel (max_vfs=N),
control it via ethtool, and then access the queues via userspace VF
drivers? If so, how would this differ from the bifurcated driver?

Cheers,
-Luke