DPDK patches and discussions
 help / color / mirror / Atom feed
From: 최익성 <pnk003@naver.com>
To: McnamaraJohn <john.mcnamara@intel.com>,
	 De Lara GuarchPablo <pablo.de.lara.guarch@intel.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
Date: Mon, 19 Oct 2015 23:48:43 +0900 (KST)	[thread overview]
Message-ID: <f3b1507a27ff4cf043ad3ade7eed6d1@cweb16.nm.nhnsystem.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202382C95@IRSMSX103.ger.corp.intel.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 14256 bytes --]

 Dear DPDK experts.
 
Thank you very much for your best great efforts and precious answers.
 
As you suggested, I reinstalled newer version of Fedora 22.
 
I succeeded to communicate test-pmd in Fedora 22 (linux kernel version 4.2.3-200.fc22.x86_64, DPDK 2.1.0).
 
The steps are as follows.
 
 
sudo yum install gcc
sudo yum install kernel-devel
sudo yum install libpcap-devel 
 
And then I patched the source codes as in  http://dpdk.org/dev/patchwork/patch/6800/   Patchwork [dpdk-dev] kni: fix igb build with kernel 4.2.
 
And then, I followed the quick start instructions from http://dpdk.org/doc/quick-start .
 
The test-pmd example seems to work.
 
Thank you very much.
 
 
 
I have another problem.
 
As in the following test-pmd log scripts, most of received packets are RX-error.
 
The same errors are occurred in the Ubuntu OS computer (Ubuntu 14.04.1 LTS, kernel version : 3.13.0-34-generic, DPDK 2.1.0).  
 
If you have any advices or answers for the above problem, I will really appreciate.
 
Thank you very much.
 
Sincerely Yours,
 
Ick-Sung Choi.
 
 
----------------------------------------------------------------------
test-pmd scripts:
 
 
$ sudo ./build/app/testpmd -c 0xFF -n 4 -- -i --portmask=0x3 --nb-cores=2
 
 
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 8 on socket 0
EAL: Detected lcore 6 as core 9 on socket 0
EAL: Detected lcore 7 as core 10 on socket 0
EAL: Detected lcore 8 as core 11 on socket 0
EAL: Detected lcore 9 as core 12 on socket 0
EAL: Detected lcore 10 as core 0 on socket 1
EAL: Detected lcore 11 as core 1 on socket 1
EAL: Detected lcore 12 as core 2 on socket 1
EAL: Detected lcore 13 as core 3 on socket 1
EAL: Detected lcore 14 as core 4 on socket 1
EAL: Detected lcore 15 as core 8 on socket 1
EAL: Detected lcore 16 as core 9 on socket 1
EAL: Detected lcore 17 as core 10 on socket 1
EAL: Detected lcore 18 as core 11 on socket 1
EAL: Detected lcore 19 as core 12 on socket 1
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 20 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x54000000 bytes
EAL: Virtual area found at 0x7f678a000000 (size = 0x54000000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f6789800000 (size = 0x600000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f6789000000 (size = 0x600000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f6788600000 (size = 0x800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f6788200000 (size = 0x200000)
EAL: Ask a virtual area of 0x9c400000 bytes
EAL: Virtual area found at 0x7f66ebc00000 (size = 0x9c400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66eb800000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66eb400000 (size = 0x200000)
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7f66e9600000 (size = 0x1c00000)
EAL: Ask a virtual area of 0x1200000 bytes
EAL: Virtual area found at 0x7f66e8200000 (size = 0x1200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f66e7c00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f66e7600000 (size = 0x400000)
EAL: Ask a virtual area of 0x3800000 bytes
EAL: Virtual area found at 0x7f66e3c00000 (size = 0x3800000)
EAL: Ask a virtual area of 0x5000000 bytes
EAL: Virtual area found at 0x7f66dea00000 (size = 0x5000000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66de600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66de200000 (size = 0x200000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f66dd400000 (size = 0xc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66dd000000 (size = 0x200000)
EAL: Ask a virtual area of 0xa00000 bytes
EAL: Virtual area found at 0x7f66dc400000 (size = 0xa00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66dc000000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f66dba00000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66db600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f66db200000 (size = 0x200000)
EAL: Ask a virtual area of 0xf4000000 bytes
EAL: Virtual area found at 0x7f65e7000000 (size = 0xf4000000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65e6a00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65e6400000 (size = 0x400000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f65e5c00000 (size = 0x600000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f65e4e00000 (size = 0xc00000)
EAL: Ask a virtual area of 0x3a00000 bytes
EAL: Virtual area found at 0x7f65e1200000 (size = 0x3a00000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f65e0a00000 (size = 0x600000)
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7f65dec00000 (size = 0x1c00000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65de600000 (size = 0x400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f65dd800000 (size = 0xc00000)
EAL: Ask a virtual area of 0xe00000 bytes
EAL: Virtual area found at 0x7f65dc800000 (size = 0xe00000)
EAL: Ask a virtual area of 0x1400000 bytes
EAL: Virtual area found at 0x7f65db200000 (size = 0x1400000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f65da400000 (size = 0xc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f65da000000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65d9a00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f65d9400000 (size = 0x400000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: Requesting 2048 pages of size 2MB from socket 1
EAL: TSC frequency is ~2793270 KHz
EAL: Master lcore 0 is ready (tid=e0bfb8c0;cpuset=[0])
EAL: lcore 7 is ready (tid=d63cb700;cpuset=[7])
EAL: lcore 4 is ready (tid=d7bce700;cpuset=[4])
EAL: lcore 6 is ready (tid=d6bcc700;cpuset=[6])
EAL: lcore 2 is ready (tid=decf8700;cpuset=[2])
EAL: lcore 3 is ready (tid=d83cf700;cpuset=[3])
EAL: lcore 5 is ready (tid=d73cd700;cpuset=[5])
EAL: lcore 1 is ready (tid=df4f9700;cpuset=[1])
EAL: PCI device 0000:04:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:04:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de000000
EAL:   PCI memory mapped at 0x7f67de080000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 0 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de084000
EAL:   PCI memory mapped at 0x7f67de104000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 1 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.0 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de108000
EAL:   PCI memory mapped at 0x7f67de188000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 5
PMD: eth_ixgbe_dev_init(): port 2 vendorID=0x8086 deviceID=0x10fb
EAL: PCI device 0000:81:00.1 on NUMA socket 1
EAL:   probe driver: 8086:10fb rte_ixgbe_pmd
EAL:   PCI memory mapped at 0x7f67de18c000
EAL:   PCI memory mapped at 0x7f67de20c000
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 3 vendorID=0x8086 deviceID=0x10fb
Interactive-mode selected
previous number of forwarding ports 4 - changed to number of configured ports 2
Configuring Port 0 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77ed9c0 hw_ring=0x7f66e77efa00 dma_addr=0x7effefa00
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e77dd0c0 sw_sc_ring=0x7f66e77dcb80 hw_ring=0x7f66e77dd600 dma_addr=0x7effdd600
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 0: 90:E2:BA:8B:BF:C0
Configuring Port 1 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77ca8c0 hw_ring=0x7f66e77cc900 dma_addr=0x7effcc900
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e77b9fc0 sw_sc_ring=0x7f66e77b9a80 hw_ring=0x7f66e77ba500 dma_addr=0x7effba500
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 1: 90:E2:BA:8B:BF:C1
Configuring Port 2 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77a77c0 hw_ring=0x7f66e77a9800 dma_addr=0x7effa9800
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e7796ec0 sw_sc_ring=0x7f66e7796980 hw_ring=0x7f66e7797400 dma_addr=0x7eff97400
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 2: 90:E2:BA:8B:B8:CC
Configuring Port 3 (socket 0)
PMD: ixgbe_dev_tx_queue_setup(): sw_ring=0x7f66e77846c0 hw_ring=0x7f66e7786700 dma_addr=0x7eff86700
PMD: ixgbe_set_tx_function(): Using simple tx code path
PMD: ixgbe_set_tx_function(): Vector tx enabled.
PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7f66e7773dc0 sw_sc_ring=0x7f66e7773880 hw_ring=0x7f66e7774300 dma_addr=0x7eff74300
PMD: ixgbe_set_rx_function(): Vector rx enabled, please make sure RX burst size no less than 32.
Port 3: 90:E2:BA:8B:B8:CD
Checking link statuses...
Port 0 Link Up - speed 10000 Mbps - full-duplex
Port 1 Link Up - speed 10000 Mbps - full-duplex
Port 2 Link Down
Port 3 Link Down
Done
testpmd&gt; start tx_first  io packet forwarding - CRC stripping disabled - packets/burst=32
  nb forwarding cores=2 - nb forwarding ports=2
  RX queues=1 - RX desc=128 - RX free threshold=32
  RX threshold registers: pthresh=8 hthresh=8 wthresh=0
  TX queues=1 - TX desc=512 - TX free threshold=32
  TX threshold registers: pthresh=32 hthresh=0 wthresh=0
  TX RS bit threshold=32 - TXQ flags=0xf01
testpmd&gt; testpmd&gt; testpmd&gt; stopTelling cores to stop...
Waiting for lcores to finish...
 
  ---------------------- Forward statistics for port 0  ----------------------
  RX-packets: 60646433       RX-dropped: 0             RX-total: 60646433
  RX-badcrc:  0              RX-badlen:  0             RX-error: 60646438
  RX-nombufs: 0             
  TX-packets: 60633255       TX-dropped: 0             TX-total: 60633255
  ----------------------------------------------------------------------------
 
  ---------------------- Forward statistics for port 1  ----------------------
  RX-packets: 60633255       RX-dropped: 0             RX-total: 60633255
  RX-badcrc:  0              RX-badlen:  0             RX-error: 60633258
  RX-nombufs: 0             
  TX-packets: 60646433       TX-dropped: 0             TX-total: 60646433
  ----------------------------------------------------------------------------
 
  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
  RX-packets: 121279688      RX-dropped: 0             RX-total: 121279688
  TX-packets: 121279688      TX-dropped: 0             TX-total: 121279688
  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Done.
testpmd&gt; testpmd&gt; quitStopping port 0...done
Stopping port 1...done
Stopping port 2...done
Stopping port 3...done
bye...
 
 
 
 
 
 
 
-----Original Message-----
From: "Mcnamara, John"&lt;john.mcnamara@intel.com&gt; 
To: "???"&lt;pnk003@naver.com&gt;; "De Lara Guarch, Pablo"&lt;pablo.de.lara.guarch@intel.com&gt;; "dev@dpdk.org"&lt;dev@dpdk.org&gt;; 
Cc: 
Sent: 2015-10-15 (목) 17:10:48
Subject: RE: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in Fedora OS release 20 (Heisenbug). I cannot r
 
&gt; -----Original Message-----

&gt; From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ???

&gt; Sent: Thursday, October 15, 2015 2:02 AM

&gt; To: De Lara Guarch, Pablo; dev@dpdk.org

&gt; Subject: Re: [dpdk-dev] I have a problem in setting up DPDK 2.1.0 in

&gt; Fedora OS release 20 (Heisenbug). I cannot r

&gt;

&gt; I checked what you mentioned.

&gt; 

&gt; * Fedora Linux kernel version is as follows.

&gt; 

&gt;      $ uname -r (print kernel name)

&gt;      3.17.7-200.fc20.x86_64



Hi,



This may be a known issue. See:





http://dpdk.org/doc/guides/rel_notes/known_issues.html#devices-bound-to-igb-uio-with-vt-d-enabled-do-not-work-on-linux-kernel-3-15-3-17





"Devices bound to igb_uio with VT-d enabled do not work on Linux kernel 3.15-3.17



Description:

    When VT-d is enabled (iommu=pt intel_iommu=on), devices are 1:1 mapped. In the Linux kernel unbinding devices from drivers removes that mapping which result in IOMMU errors. Introduced in Linux kernel 3.15 commit, solved in Linux kernel 3.18 commit."



John

\x16º&¶\x1a&jɨž6¥¢~°Šw\¢c(œç-×Ý{ÓMûÛMyEën®sÚ¶^[a¢f¬š‰ãjZ'ë\b§uÊ&Eç\x1eŠ÷~º&™¨¥•½\x1f׿ ¢ˆ%yÊ&™¨¥•½\x1f׿ ¢ˆ%yÊ&ÛO|çm{׿^[ÉÚ]’Šà>‹-~,pŠØDHÄω޽÷nAëgè­×¯v—d¢¸\f¢}}9ËvÓ^uïM7ïí6Ó@„I4^qè¯yÖò•¶ðo|"¶\x14ŒLøÁ½ì£Î<ómùÖVÛÕú+uëÝ¥Ù(®\x03(Ÿ_Nrݴם<ÓMûÓ½4<4×\x1aŠ •àÊ Ä¢‚v­º·¯

      parent reply	other threads:[~2015-10-19 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  1:29 최익성
2015-10-14  1:38 ` Xu, Qian Q
2015-10-14  1:49 ` 최익성
2015-10-14 13:19   ` De Lara Guarch, Pablo
2015-10-15  1:01     ` 최익성
2015-10-15  8:02       ` De Lara Guarch, Pablo
2015-10-15  8:10       ` Mcnamara, John
2015-10-15 23:46         ` 최익성
2015-10-19 14:48         ` 최익성 [this message]

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=f3b1507a27ff4cf043ad3ade7eed6d1@cweb16.nm.nhnsystem.com \
    --to=pnk003@naver.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=pablo.de.lara.guarch@intel.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).