DPDK patches and discussions
 help / color / mirror / Atom feed
From: Masaru Oki <m-oki@stratosphere.co.jp>
To: Fred Pedrisa <fredhps10@hotmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] hw.nic_uio.bdfs
Date: Wed, 26 Mar 2014 15:42:40 +0900	[thread overview]
Message-ID: <CAFLKUz+9Wko3_73XUADKP+gttMpWFLPxma=jA+QQ=uwELY7bmQ@mail.gmail.com> (raw)
In-Reply-To: <COL131-DS10C032EEFFC3DF69D14D4FB0640@phx.gbl>

avoid??? want you hw.nic_uio.avoid_bdfs?

nic_uio behavior I guessed
1. detach kernel driver specified by hw.nic_uio.bdfs
2. attach nic_uio driver for all NICs not attached.
but 2. is not correct, I think.



2014-03-26 15:20 GMT+09:00 Fred Pedrisa <fredhps10@hotmail.com>:

> Hello,
>
>
>
> You did not understand the purpose of that parameter, it is made to
> 'avoid' nic_uio from pursuing the wanted NICs... so they are free to be
> used in the system :)
>
>
>
> Right now the code to handle it is wrong and I am trying to fix it myself.
>
>
>
> *De:* Masaru Oki [mailto:m-oki@stratosphere.co.jp]
> *Enviada em:* quarta-feira, 26 de março de 2014 03:16
> *Para:* Fred Pedrisa
> *Cc:* dev@dpdk.org
> *Assunto:* Re: [dpdk-dev] hw.nic_uio.bdfs
>
>
>
> Hi,
>
> I tried with Intel version 1.6.0 and FreeBSD 9.2-RELEASE on VMware Player.
>
> kldload nic_uio by hand, works fine.
> But kldunload nic_uio only detach uio driver, don't re-attach kernel
> driver.
>
> [oki@ ~]$ cat /boot/loader.conf
> ##############################################################
> ###  User settings  ##########################################
> ##############################################################
> hw.contigmem.num_buffers=64
> hw.contigmem.buffer_size=2097152
> hw.nic_uio.bdfs="2:5:0,2:6:0"
> contigmem_load="YES"
> #nic_uio_load="YES"
> [oki@ ~]$ pciconf -l | egrep '(em|uio)'
> em0@pci0:2:1:0: class=0x020000 card=0x075015ad chip=0x100f8086 rev=0x01
> hdr=0x00
> em1@pci0:2:5:0: class=0x020000 card=0x075015ad chip=0x100f8086 rev=0x01
> hdr=0x00
> em2@pci0:2:6:0: class=0x020000 card=0x075015ad chip=0x100f8086 rev=0x01
> hdr=0x00
> [oki@ ~]$ kenv hw.nic_uio.bdfs
> 2:5:0,2:6:0
> [oki@ ~]$ sudo kldload nic_uio
> Password:
> [oki@ ~]$ pciconf -l | egrep '(em|uio)'
> em0@pci0:2:1:0: class=0x020000 card=0x075015ad chip=0x100f8086 rev=0x01
> hdr=0x00
> nic_uio0@pci0:2:5:0:    class=0x020000 card=0x075015ad chip=0x100f8086
> rev=0x01 hdr=0x00
> nic_uio1@pci0:2:6:0:    class=0x020000 card=0x075015ad chip=0x100f8086
> rev=0x01 hdr=0x00
> [oki@ ~]$ sudo kldunload nic_uio
> [oki@ ~]$ pciconf -l | egrep '(em|uio)'
> em0@pci0:2:1:0: class=0x020000 card=0x075015ad chip=0x100f8086 rev=0x01
> hdr=0x00
> [oki@ ~]$
>
>
>
> 2014-03-26 14:35 GMT+09:00 Fred Pedrisa <fredhps10@hotmail.com>:
>
> Hi, guys.
>
>
>
>
> This variable is not working as intended for FreeBSD :(
>
>
>
> It does not dettach nic_uio from the wanted ports :/
>
>
>
>

  reply	other threads:[~2014-03-26  6:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  5:35 Fred Pedrisa
2014-03-26  6:15 ` Masaru Oki
     [not found] ` <013601cf48bb$0e1ed6a0$2a5c83e0$@stratosphere.co.jp>
2014-03-26  6:20   ` [dpdk-dev] RES: hw.nic_uio.bdfs Fred Pedrisa
2014-03-26  6:42     ` Masaru Oki [this message]
     [not found]     ` <014d01cf48be$f02c3990$d084acb0$@stratosphere.co.jp>
2014-03-26  6:49       ` Fred Pedrisa
2014-03-26  6:52         ` [dpdk-dev] RES: " Fred Pedrisa
2014-03-26  7:07         ` [dpdk-dev] hw.nic_uio.bdfs Masaru Oki
     [not found]         ` <016201cf48c2$59f0ead0$0dd2c070$@stratosphere.co.jp>
2014-03-26  7:16           ` [dpdk-dev] RES: hw.nic_uio.bdfs Fred Pedrisa
     [not found]           ` <016f01cf48c3$99aedc30$cd0c9490$@hotmail.com>
2014-03-26  7:22             ` [dpdk-dev] RES: " Fred Pedrisa
2014-04-17 14:05               ` Thomas Monjalon
     [not found]             ` <017001cf48c4$4439eaf0$ccadc0d0$@hotmail.com>
2014-03-26  7:51               ` [dpdk-dev] RES: " Fred Pedrisa

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='CAFLKUz+9Wko3_73XUADKP+gttMpWFLPxma=jA+QQ=uwELY7bmQ@mail.gmail.com' \
    --to=m-oki@stratosphere.co.jp \
    --cc=dev@dpdk.org \
    --cc=fredhps10@hotmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).