All of lore.kernel.org
 help / color / mirror / Atom feed
From: 安宏奎 <anhk_-KN7UnAbNpbg@public.gmane.org>
To: "'Marc Sune'" <marc.sune-kpkqNMk1I7M@public.gmane.org>,
	<dev-VfR2kkLFssw@public.gmane.org>
Subject: 答复:  Port-ids and NIC features
Date: Thu, 15 Aug 2013 09:51:00 +0800	[thread overview]
Message-ID: <008101ce9959$e4959370$adc0ba50$@126.com> (raw)
In-Reply-To: <520B4641.2030802-kpkqNMk1I7M@public.gmane.org>

For the question one, maybe you can detect it before binding to igb_uio


-----邮件原件-----
发件人: dev-bounces-VfR2kkLFssw@public.gmane.org [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] 代表 Marc Sune
发送时间: 2013年8月14日 16:57
收件人: dev-VfR2kkLFssw@public.gmane.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.

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)?

Best
marc

  parent reply	other threads:[~2013-08-15  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  8:56 Port-ids and NIC features Marc Sune
     [not found] ` <520B4641.2030802-kpkqNMk1I7M@public.gmane.org>
2013-08-15  1:51   ` 安宏奎 [this message]
2013-08-15 14:57     ` 答复: " Stephen Hemminger
     [not found]       ` <20130815075704.33261119-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-08-15 22:15         ` Marc Sune
     [not found]           ` <520D52E8.9000407-kpkqNMk1I7M@public.gmane.org>
2013-08-15 23:31             ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='008101ce9959$e4959370$adc0ba50$@126.com' \
    --to=anhk_-kn7unabnpbg@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=marc.sune-kpkqNMk1I7M@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.