From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrien Mazarguil Subject: Re: [PATCH 1/1] net/mlx4: add port parameter Date: Thu, 16 Mar 2017 12:04:09 +0100 Message-ID: <20170316110409.GO3790@6wind.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, Nelio Laranjeiro , "Legacy, Allain" , Stephen Hemminger To: Gaetan Rivet Return-path: Received: from mail-wr0-f172.google.com (mail-wr0-f172.google.com [209.85.128.172]) by dpdk.org (Postfix) with ESMTP id 210C82BF3 for ; Thu, 16 Mar 2017 12:04:18 +0100 (CET) Received: by mail-wr0-f172.google.com with SMTP id u108so29248473wrb.3 for ; Thu, 16 Mar 2017 04:04:18 -0700 (PDT) Content-Disposition: inline In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Mar 03, 2017 at 04:40:06PM +0100, Gaetan Rivet wrote: > Most ConnectX-3 adapters expose two physical ports on a single PCI bus > address. > > Add a new port parameter allowing the user to choose > either or both physical ports to be used by the application. > > This parameter is used as follows: > > Selecting only the second port: > -w 00:00.0,port=1 > > Selecting both ports: > -w 00:00.0,port=0,port=1 > > If no parameter is given, the default behavior is unchanged: all ports > are probed. > > Signed-off-by: Gaetan Rivet I think this patch is good as is. Whatever value results from users specifying random characters as argument to the port parameter is their problem, as long as the resulting value is verified to be within bounds, it's fine. I'm not saying that checking all possible failure modes of strtoul() is useless, just that it seems overkill in this specific case. Using atoi() without any error checking would have been perfectly fine as well. Acked-by: Adrien Mazarguil -- Adrien Mazarguil 6WIND