From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by dpdk.org (Postfix) with ESMTP id 386F37EC4 for ; Fri, 7 Nov 2014 14:49:49 +0100 (CET) Received: by mail-wi0-f172.google.com with SMTP id bs8so4649998wib.5 for ; Fri, 07 Nov 2014 05:59:21 -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=0Hwv0nDlmJFiL5iBoFI2NiEq5gGen3jKyV3qrb51xcI=; b=LRrgPPEa1IZBxCS1NF/L7FfXBoNjfXW21VuBzk7E+74F7Q7DIUgXliu2NLsx06Onjw voqdaBgvpfQEzHJXIl6opISvMr2X+3Anr4fmZj0YJc1dyXP7djHuUFVMtzBPeXqrktNE fwmHPDuWTgkR4pxBYD9mYkvcL5WxZ62OT9pVpyPrhWaAF1u1XIGPQO3SKygFdE8ysno7 2ZoKU3ZhtOVx160dgd3iE3NdNV0Hi0NMUOYAC61k/zrW9mOfgqlUZhzHzsz/BlyArqol tWLw/Pchtj1z7Q76sjeIXG0DY5mrj1vz7ZyWLRediXd8kyEVj9aca1CzXcmaeLBsXv2M DPOw== X-Gm-Message-State: ALoCoQkCQe1TiaQmCplcPHB3iJ4+inNBBfBu0xFFlQtXQ0oWU7IJV8N+ZD+yO0yUMxtMlRh/ZZ+O X-Received: by 10.194.60.45 with SMTP id e13mr16578974wjr.109.1415368761184; Fri, 07 Nov 2014 05:59:21 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id x3sm2166345wiy.4.2014.11.07.05.59.19 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Nov 2014 05:59:20 -0800 (PST) From: Thomas Monjalon To: Nicolas Pernas Maradei Date: Fri, 07 Nov 2014 14:59:01 +0100 Message-ID: <2501357.jaIIFMyNbY@xps13> Organization: 6WIND User-Agent: KMail/4.14.2 (Linux/3.17.2-1-ARCH; KDE/4.14.2; x86_64; ; ) In-Reply-To: <545CCBA8.7030900@emutex.com> References: <545CBCE0.2030806@emutex.com> <20141107132618.GD25469@hmsreliant.think-freely.org> <545CCBA8.7030900@emutex.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] White listing a virtual device 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: Fri, 07 Nov 2014 13:49:49 -0000 2014-11-07 13:39, Nicolas Pernas Maradei: > On 07/11/14 13:26, Neil Horman wrote: > > Then you create the pcap device with --vdev, and simply don't load the pmds for > > any of your physical devices (or just don't use pci-whitelist at all if you're > > doing a static build). If you do that, then the corresponding niantic driver > > won't initialize any of the hardware, you'll only get the pcap port. > > What you are saying is just another way to black list the ports I don't > want to use. I'm aware of that option (as well as using the -b option) > but in our particular case we have several systems under test with > different configurations and we want to use this virtual port only. > Which seems to be a perfect use case for white listing rather than black > listing or modifying the system configuration. Sorry I don't understand why you don't want to use the blacklist option. -- Thomas