From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by dpdk.org (Postfix) with ESMTP id 9B86E8D8D for ; Thu, 1 Oct 2015 12:55:19 +0200 (CEST) Received: by wiclk2 with SMTP id lk2so27161114wic.0 for ; Thu, 01 Oct 2015 03:55:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=83L8GX19ohlMoBsoLMDl2TykEwcXuXJpOlrjeSE7nRU=; b=EXvSr/UPh2tr+97mYhekkHwX0CIqs0u2qgm27WBkJSA29Atk5p4Sa+WoaimfpTGJ15 BOiqVLBZ/IpSsS9D6tgfHn1zea5Puz+KpbCVFXUO2AblUG8jkExd1YZdNhpd9KoSuVqt rTzrpJzznXms/WqMAVCoiV9uPEDSl1MsLysyXzOGYLZFSv5pCwZ0iA8Pw7RAJ/hyBFPc 3anaam+uGTddjqDaNz7EqUQZ90Opqi1dXbtatW3RM42MH3de9A5DDv8eJRQF6m5thQ6z 9q3MAICQS7G9EdyKk7K6D0to34dxBoQX2DjgYFjozwuP8Dg/SiUn8zZiHhsvd23uXgBk TnVg== X-Gm-Message-State: ALoCoQlJPEYr4IVqGiVak7Yu/4Oq2+S6d+31QuSmkbB8KdAaRQT7+nuexDEtqLr+h6m8iA/nMO9y X-Received: by 10.194.246.102 with SMTP id xv6mr9690108wjc.58.1443696919396; Thu, 01 Oct 2015 03:55:19 -0700 (PDT) Received: from avi.cloudius ([37.142.229.250]) by smtp.googlemail.com with ESMTPSA id ry1sm5516706wjb.24.2015.10.01.03.55.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2015 03:55:17 -0700 (PDT) To: "Michael S. Tsirkin" References: <20150930204016.GA29975@redhat.com> <20151001113828-mutt-send-email-mst@redhat.com> <560CF44A.60102@scylladb.com> <20151001120027-mutt-send-email-mst@redhat.com> <560CFB66.5050904@scylladb.com> <20151001123335-mutt-send-email-mst@redhat.com> <560D028A.8050509@scylladb.com> <20151001131517-mutt-send-email-mst@redhat.com> <560D09E4.4060603@scylladb.com> <560D0A0D.8030604@scylladb.com> <20151001133906-mutt-send-email-mst@redhat.com> From: Avi Kivity Message-ID: <560D1113.7080202@scylladb.com> Date: Thu, 1 Oct 2015 13:55:15 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <20151001133906-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Having troubles binding an SR-IOV VF to uio_pci_generic on Amazon instance 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: Thu, 01 Oct 2015 10:55:19 -0000 On 10/01/2015 01:44 PM, Michael S. Tsirkin wrote: > On Thu, Oct 01, 2015 at 01:25:17PM +0300, Avi Kivity wrote: >> Why use a VF on a non-virtualized system? > 1. So a userspace bug does not destroy your hardware > (PFs generally assume trusted non-buggy drivers, VFs > generally don't). People who use dpdk trust their drivers (those drivers are the reason for the system to exist in the first place). > 2. So you can use a PF or another VF for regular networking. This is valid, but usually those systems have a separate management network. Unfortunately VFs limit the number of queues you can expose, making them less performant than PFs. The "bifurcated drivers" were meant as a way of enabling this functionality without resorting to VFs, but it seems they are stalled. > 3. So you can manage this system, to some level. > Again existing practice doesn't follow this.