From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 030C32C24 for ; Wed, 1 Aug 2018 17:56:29 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9FD3321785; Wed, 1 Aug 2018 11:56:28 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 01 Aug 2018 11:56:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Di8m7el2Ur5jqobvFGVenFmw5V cFH6PwXxre5yjnwGM=; b=IXxlNqB7fGusS2kWWiHi8G57mA1X+hO+W/KQYRBkZg WsCvSK3mDH0U5ZWqsl77on07qxw/4tPIe5IG5bPRDLQ4ChWd38Oxbc/c5p0gvt0h 3kP4Mgt3PpnOv/e2WKG+kC9WRKcZ/lPTvaZOFhfgwEiU7q3gqPl4niM3hdUKIhqy c= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Di8m7e l2Ur5jqobvFGVenFmw5VcFH6PwXxre5yjnwGM=; b=U4NcXcE05672GSBSWBNm8K fAXJhyW3KyrdpFIbPbVIGSNR2vUqrNqbxhvW1YPqszsAaySCyXWpIxqm4HNpf0Rn l/RoqmFNhC+Hm7lAOBUiqdK6Wy2dMYlSPIA3PWmjelDwjsStdA9yxw8jM9Lkw9lO 5rrZ+NZ2rgj0H8hG0cUx3CzK9p21GenfsoG0+tNoeXmssnQzksuGZbWR/6Kw9+e7 B/6bGitcRIwob3fESHXPyMfbf3nng+gzJSJtyZjzGaa/Gv9lMtKc+s2LbkeVHIhS MsygOhMIxn1HfIYrmEmQk9IcfzqxIukiyzK74WR85Lz7RuYZqiB4gyA1L3Udsibg == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BCD5310276; Wed, 1 Aug 2018 11:56:27 -0400 (EDT) From: Thomas Monjalon To: cristian.dumitrescu@intel.com Cc: dev@dpdk.org, Kevin Laatz Date: Wed, 01 Aug 2018 17:56:23 +0200 Message-ID: <4025558.pA2mlQF48x@xps> In-Reply-To: <20180720130906.82895-1-kevin.laatz@intel.com> References: <20180720130906.82895-1-kevin.laatz@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: include note for pci address naming in ip pipeline X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Aug 2018 15:56:29 -0000 Cristian, review please? 20/07/2018 15:09, Kevin Laatz: > Add a note to the 'link' command in the IP Pipeline documentation > specifying the PCI device name format required to run the application. > > Signed-off-by: Kevin Laatz > --- > doc/guides/sample_app_ug/ip_pipeline.rst | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst > index 660798d..dc6a3b9 100644 > --- a/doc/guides/sample_app_ug/ip_pipeline.rst > +++ b/doc/guides/sample_app_ug/ip_pipeline.rst > @@ -222,6 +222,7 @@ Link > txq promiscuous on | off > [rss ... ] > > + Note: The PCI device name must be specified in the Domain:Bus:Device.Function format. > > Mempool > ~~~~~~~ >