From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gaetan.rivet@6wind.com> Received: from mail-wr0-f177.google.com (mail-wr0-f177.google.com [209.85.128.177]) by dpdk.org (Postfix) with ESMTP id D1B4B1B2BE for <dev@dpdk.org>; Thu, 18 Jan 2018 10:46:36 +0100 (CET) Received: by mail-wr0-f177.google.com with SMTP id t16so8209455wrc.10 for <dev@dpdk.org>; Thu, 18 Jan 2018 01:46:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=gtaq0ryzXtTqXedUothoFJp+SFQ8YBzQCkrtD23iQb4=; b=uGjJnJW43GK5ifZrANIUUSSTQ2Zo8FKm25ySXGOTvlisXeNaswYk7JXkDbaFCp0uQM V7wlQHLU2tMI9ln1RRdhEbwm36VU9ggVsdE6/l7UsJ4jhnTeQRBmRWXqU3A+HTD4/1RY CqJrQ++zpZsyqjxcqBQXQNlqqD3SIJC91uzKL54VJo2aWIiDQ0Z6hqGK5WC1ZZQ1mwlE ygV1KkaqUc2nzmnky222lqGa5Sldb2oP/UhulP0uxydDnIb5g6jZ4Gi0UOtZdaVXIN/o 2964P1YCo0lf6BffHXsptpUzxDGL+5J3CtqYTpb0hqvPYoYUd+zVcWCo4KfkHkqTX+5E wQFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=gtaq0ryzXtTqXedUothoFJp+SFQ8YBzQCkrtD23iQb4=; b=BYPF6iInfqkUjagOss7g9iB68BsOzyx1LVVop/LO5mm6DHsD4Zdu6q2fUBlCkOT76f 3FgbiNS0iAGSquFnEyPmXjb0ggiFDS96nnQXR6KljzqYaLmR99OLNfGU++h0a1RoaD4V Kf/0fRelWkGnaHTrkx16fKz1bPZi13QqhuVlEiNsCeRSIJklfgUriorCGxGjSQsSLIFL +khnAHgF10s9DMPOhWNqU/KsUk2m7sb5iQxx3dX0oV6ZwNt8Dt6Xi1Y2fU/88lzX8d1O PuIBA3EKX5SxNv0vnROoQnHpqRgM10+By5YHSR3/IQvK0GdjXaIlzhnScKpfOsMY61Of +Hew== X-Gm-Message-State: AKwxytfifq5f3DvBJp/h9BzUiqFyCDVYo4QqExk6K53/gsqZopl2CKUV hD6EByi0PIXPU6ZpybMK40Pm7A== X-Google-Smtp-Source: ACJfBoswdDMcvGHznfPbpIPVAWt7XU9jn+Xllrt0dDmzSUMytFF+Aku+2i0p2MEsN2wHqX4Vms3Fmw== X-Received: by 10.223.200.141 with SMTP id k13mr5332512wrh.216.1516268796319; Thu, 18 Jan 2018 01:46:36 -0800 (PST) Received: from bidouze.vm.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id h194sm17674892wma.8.2018.01.18.01.46.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 18 Jan 2018 01:46:35 -0800 (PST) Date: Thu, 18 Jan 2018 10:46:23 +0100 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet <gaetan.rivet@6wind.com> To: Thomas Monjalon <thomas@monjalon.net> Cc: Yuanhan Liu <yliu@fridaylinux.org>, Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org Message-ID: <20180118094623.gu5ahrfd75b5gcct@bidouze.vm.6wind.com> References: <1516114218-21501-1-git-send-email-yliu@fridaylinux.org> <68453aa8-de09-c41b-0b84-82eb6bbe19ac@intel.com> <20180118073520.GZ29540@yliu-mob> <1649717.sl7PR1QSdr@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1649717.sl7PR1QSdr@xps> User-Agent: NeoMutt/20170113 (1.7.2) Subject: Re: [dpdk-dev] [PATCH] doc: document the new devargs syntax X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://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: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 18 Jan 2018 09:46:37 -0000 On Thu, Jan 18, 2018 at 09:46:29AM +0100, Thomas Monjalon wrote: > 18/01/2018 08:35, Yuanhan Liu: > > On Wed, Jan 17, 2018 at 12:34:08PM +0000, Ferruh Yigit wrote: > > > So does it make sense to separate them logically? Perhaps as "device identifier" > > > and "device args". > > > > Then I think it returns back to the old issue: how could we identify a > > port when the bus id (say BDF for PCI bus) is not enough for identifying > > a port? Such case could happen when a single NIC has 2 ports sharing > > the same BDF. It could also happen with the VF representors that will > > be introduced shortly. > > Yes, the device matching syntax must include bus category, class category > and driver category. So any device can be identified in future. > > But I think Ferruh is talking about separating device matching > (which is described in this proposal) and device settings > (which are usually mixed in -w and --vdev options). > I agree there are different things and may be separate. > They could share the same syntax (bus/class/driver) but be separate > with a semicolon: > matching;settings Can you give an example? -- Gaëtan Rivet 6WIND