All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Lyn M <netinal7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: l3fwd error, port 0 is not present on the board
Date: Tue, 06 Jan 2015 10:02:25 +0100	[thread overview]
Message-ID: <1613023.VipzgMKAkl@xps13> (raw)
In-Reply-To: <CAM8Q2aXd0++=JCrMO7pq9Ai+TufXHcZs4H0O00L0N12fHpcdBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

2015-01-02 09:07, Lyn M:
> In my original post, I thought my choice of hex portmask -p 0x3 was causing
> this issue -- now I know that was not the case.  But, I am still curious
> about how the hex portmask is determined.  Since I only have two ports
> bound to igb_uio, my hex postmask will always be 0x3?  What if I choose to
> bind other ports to igb_uio?  Is there a Linux command I can run to
> determine what mask to use with the -p option?

That's something which could be done.
Port numbering is defined by probing order. Does a tool showing the (dry-run)
probed devices, their number and mask, would help you?
By the way, you are welcome to try developing it.

-- 
Thomas

  parent reply	other threads:[~2015-01-06  9:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 20:18 l3fwd error, port 0 is not present on the board Lyn M
     [not found] ` <CAM8Q2aVXRMbJZ3u25u_P1hwy_acGGvBQEQr8-CLmWwNK-HPfNg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-29 21:02   ` Neil Horman
     [not found]     ` <20141229210210.GA31480-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-12-30 18:54       ` Lyn M
     [not found]         ` <CAM8Q2aXo5RhtrYnV+SSB_gDkG5OeZ-BCDqib+xaGG84rmRK2iQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-30 21:24           ` Neil Horman
     [not found]             ` <20141230212406.GB2187-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-12-31 14:18               ` Lyn M
     [not found]                 ` <CAM8Q2aUYDQ-+wkLn9hPTNKQnLwBqJOcA2tTO=WFt3eY-sUXnyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-31 14:48                   ` Neil Horman
     [not found]                     ` <20141231144859.GA6637-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2014-12-31 16:50                       ` Lyn M
     [not found]                         ` <CAM8Q2aXiXv+WBQPg5PLn7aGp_2V=a=Rcm1vPrXC2u5EycLaZfw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-01  3:37                           ` Neil Horman
     [not found]                             ` <20150101033744.GA8149-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-01-01  4:00                               ` Neil Horman
     [not found]                                 ` <20150101040032.GA11645-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2015-01-02 15:07                                   ` Lyn M
2015-01-04  3:50                                     ` Qiu, Michael
     [not found]                                     ` <CAM8Q2aXd0++=JCrMO7pq9Ai+TufXHcZs4H0O00L0N12fHpcdBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-02 19:54                                       ` Neil Horman
2015-01-06  9:02                                       ` Thomas Monjalon [this message]
2015-01-06  9:41                                         ` Bruce Richardson

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=1613023.VipzgMKAkl@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=netinal7-Re5JQEeQqe8AvxtiuMwx3w@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.