From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f43.google.com (mail-pb0-f43.google.com [209.85.160.43]) by dpdk.org (Postfix) with ESMTP id 57E411F3 for ; Thu, 15 Aug 2013 16:56:40 +0200 (CEST) Received: by mail-pb0-f43.google.com with SMTP id md4so812103pbc.16 for ; Thu, 15 Aug 2013 07:57:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=me7tVA0uDr9lxhYB4jpUqIAQ1GVdznr5fz+J5sq63nU=; b=H3RHgnk9/IaAoBczkoJ2j5Hp8W7B5czM6h8OHynQibOtlsJMbeyrl2yyXwEuy+eP32 +E5gvWOGjeP3wyv7XA6DuOKd8pK7xyxFsLPIAo+7lqaQOgwM06kx5NgiyIw6t3LJifW9 UckanH5IQXjLtd/rZzHhKKVGsJq4GD6Adz3ux6mTR/N/Ju/1XUei1aXxc63T78S9mEc0 6J5fFD8dxlR1o+orYSsr/WKyVDLLPVRa2en7HuutPvHoQmJhTTFyf133gi/aoZdnbCvj U5IWOCysuloravYB74etmuHPalKh1How2+UlEmKmw+l0tlmzOaitnj54NcGqwnCIhWtj rZsw== X-Gm-Message-State: ALoCoQkVlON08LdS/XV8CSHoVvoJc8UE/8v9FeVrm1cB9eNaNNLunelUMclca8was3G02h14gkld X-Received: by 10.66.50.104 with SMTP id b8mr16248999pao.39.1376578628288; Thu, 15 Aug 2013 07:57:08 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-69-237.bvtn.or.frontiernet.net. [50.53.69.237]) by mx.google.com with ESMTPSA id w6sm53812029pbt.32.2013.08.15.07.57.07 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 15 Aug 2013 07:57:07 -0700 (PDT) Date: Thu, 15 Aug 2013 07:57:04 -0700 From: Stephen Hemminger To: =?gb2312?B?sLK66r/8?= Message-ID: <20130815075704.33261119@nehalam.linuxnetplumber.net> In-Reply-To: <008101ce9959$e4959370$adc0ba50$@126.com> References: <520B4641.2030802@bisdn.de> <008101ce9959$e4959370$adc0ba50$@126.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] =?gb2312?b?tPC4tDogUG9ydC1pZHMgYW5kIE5JQyBmZWF0dXJl?= =?gb2312?b?cw==?= 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, 15 Aug 2013 14:56:40 -0000 On Thu, 15 Aug 2013 09:51:00 +0800 安宏奎 wrote: > For the question one, maybe you can detect it before binding to igb_uio > > > -----邮件原件----- > 发件人: dev-bounces@dpdk.org [mailto:dev-bounces@dpdk.org] 代表 Marc Sune > 发送时间: 2013年8月14日 16:57 > 收件人: dev@dpdk.org > 主题: [dpdk-dev] Port-ids and NIC features > > Dear all, > > Two quick questions: > > 1) Is there a way to get the features available in the NIC? In particular, I > cannot see a way to retrieve the *maximum speed* of the card and I need to > determine whether is a FE, GE or 10GE card. Not at present. You need to look at the information in rte_pci_device for the ethernet (see rte_eth_dev_info) and then do your own matching against ID and features. As DPDK evolves more of the hardware features need to be abstracted to allow applications to be build once and run on varying hardware. IMHO some of the low level features like read/write thresholds really shouldn't be exposed through the API. Setting them correctly depends too much on the underlying hardware, chip version, and driver and really shouldn't be something the application writer has to worry about. > 2) For a certain number of NICs installed in the system and bound to the > IGB_UIO driver, is it safe to assume that the association phyisical port <-> > port_id will always be the same? Even after reboot, and regardless of the > order that are bound to the IGB_UIO driver (e.g. using pci_unbind.py)? Since probe is single threaded. The discovery order will be constant on the same system. But will change if hardware added/removed. Another future area of work that needs to be addressed is hot plugging devices into a running application.