From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lukego@gmail.com>
Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45])
 by dpdk.org (Postfix) with ESMTP id 815627E7B
 for <dev@dpdk.org>; Wed, 22 Oct 2014 18:01:52 +0200 (CEST)
Received: by mail-wg0-f45.google.com with SMTP id m15so4069047wgh.4
 for <dev@dpdk.org>; Wed, 22 Oct 2014 09:10:13 -0700 (PDT)
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=yNsgkhPko7ABvGpMdhDUvfXHg0LHihwShg6Y4x1kFrE=;
 b=HAOGXJpHWNJ+BR39kI2XfM6fIsgUwpNrFx+QJkRUxqryNQtZPRDGzCQm+0X8S2TEQE
 kGGaMRxyTCuCYPajstIXipOLJkHN4PUafxN2c5hrYGv4QbITMF0vpKerByAeAfQJVm4l
 v9b5UZgKAVLBF2xQSlQ3xyG7uI4x68D+H4D8dKmwDecXGKsoEjkmAO54g1BbYwMaCP+W
 uFWEx+L9Grfose8oeDsshYBR+aYBYQOUo1JUg52Bbufx3K/yLLjyCvhxzC6a6M16ioUg
 V7XlX9BE2EHMtQo5frsa6qtfWcxGotrSGcpHPueHyx1vSAWFAo/jaoxfnVt9ew3o6Ve5
 aQ4Q==
MIME-Version: 1.0
X-Received: by 10.194.85.229 with SMTP id k5mr49896916wjz.19.1413994213434;
 Wed, 22 Oct 2014 09:10:13 -0700 (PDT)
Sender: lukego@gmail.com
Received: by 10.194.219.233 with HTTP; Wed, 22 Oct 2014 09:10:13 -0700 (PDT)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com>
References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com>
Date: Wed, 22 Oct 2014 18:10:13 +0200
X-Google-Sender-Auth: uPMQWE46eOdjPjdO5Imp_nwrReI
Message-ID: <CAA2XHbc4T4BCUA00U4_UwsakkFGSrWvPAzjosJcH3BQHN2Ahbg@mail.gmail.com>
From: Luke Gorrie <luke@snabb.co>
To: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015
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: Wed, 22 Oct 2014 16:01:52 -0000

Hi Tim,

On 22 October 2014 15:48, O'driscoll, Tim <tim.o'driscoll@intel.com> wrote:

> 2.0 (Q1 2015) DPDK Features:
> Bifurcated Driver: With the Bifurcated Driver, the kernel will retain
> direct control of the NIC, and will assign specific queue pairs to DPDK.
> Configuration of the NIC is controlled by the kernel via ethtool.
>

That sounds awesome and potentially really useful for other people writing
userspace data planes too. If I understand correctly, this way the messy
details can be contained in one place (kernel) and the application (DPDK
PMD or otherwise) will access the NIC TX/RX queue via the ABI defined in
the hardware data sheet.

Single Virtio Driver: Merge existing Virtio drivers into a single
> implementation, incorporating the best features from each of the existing
> drivers.
>

Cool. Do you have a strategy in mind already for zero-copy optimisation
with VMDq? I have seen some patches floating around for this and it's an
area of active interest for myself and others. I see a lot of potential for
making this work more effectively with some modest extensions to Virtio and
guest behaviour, and would love to meet kindred spirits who are thinking
along these lines too.