From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sonic314-13.consmr.mail.bf2.yahoo.com (sonic314-13.consmr.mail.bf2.yahoo.com [74.6.132.123]) by dpdk.org (Postfix) with ESMTP id 556FA3255 for ; Fri, 1 Sep 2017 17:52:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1504281150; bh=JUFPCdPX0myXbw4Nh0SJppzKiVlx2amxT7+U7F0n62w=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject; b=LNNANvYO/boyRr3MilUVVtlAWMJkXJbdKzCTbc4OChhJ+OTcrm795XKXVA4jhZSdUCoIk+q/J/7Ku/xqrkAP+mmO61nAvBlpa5p8Q3r/GWG0HgyDzx8RE9X2z23RUbCu8hLRjjvIqzPR5xEpfQGj0tNGVhTd5g38Wux33aoetlpA3CT50i4Dm1W8N7CMezS350b0jeHrPccaPGp3UhDK5SXbeYezVWpTJuS3VlUIY0O0ExhRhnjTAJQA7oCosoIRWs5PDJDIBCMsaj/OzWgpTxM0HYKQLDjUyCuL8l7kVUIOpGMF9/d/QnBu8FKRwDQHtC/gHOkVhaha4AfnlqmcQg== X-YMail-OSG: UEU8QqEVM1liEBnVESjsx90A7iqtSanyvrGWdY.ssYN1rJUFH8TjVfDhcGD2L8I aigzvjgFh.VSExja8895xZPbCvbroocty9KllfFqL.VhgXE_apUdcCbcf6H.Ig9SxLOHBl9F02lu DVDhwMwRKKDTxui7YfwknCi2AW1.aMnooR.pZwsr88GyFXfSHxzQ1WfNuUYJ0za5hQM7e.2b34tP qDaq_VJFyUrM3pI2Ct47QgSP_WiATqXkKXW3ojvSq5pX3Usfp44o_NOWKGgFo1N_ul8yILuz2LMm LI2_.k3zW.9RVuvY07u1tyHPAkBF68mIq1VtuaXYOD8NSgzIzJROLi15icLIE.Xiet838s53gQxm 5SpwWj2MfD8.CHZDHr2dLQ65SLqlccP6.T_Q05KshTuGY9.UGigSKKiBzb9LFcVON77Ii56xonM2 5f1PI2AZ4SX.yiHEtjolVWizEG4iwGhkXhped8BGceyE- Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.bf2.yahoo.com with HTTP; Fri, 1 Sep 2017 15:52:30 +0000 Date: Fri, 1 Sep 2017 15:52:30 +0000 (UTC) From: Dharmesh Mehta To: "users@dpdk.org" , Kyle Larose Message-ID: <1577249268.1093678.1504281150569@mail.yahoo.com> In-Reply-To: References: <800120698.826966.1504246225460.ref@mail.yahoo.com> <800120698.826966.1504246225460@mail.yahoo.com> MIME-Version: 1.0 X-Mailer: WebService/1.1.10495 YMailNorrin Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] jumbo frame support..(more than 1500 bytes) X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2017 15:52:32 -0000 Hello Kyle, Could you please tell me which DEBUG flag I should turn on it can print err= or. how do I check it is not dropping before my device? =C2=A0 Have you made sure the max frame size of every hop in between is large enou= gh? =C2=A0 =C2=A0 - can you tell me which file / debug flag I should turn on so= I get more insight. thanks,dharmesh.If you see my e-mail. setting of buffer size is done correc= tly in my main application. I hope same #define will be get picked by lib / driver etc.... during compi= lation. Do we have centralized place in DPDK where we can configure all this settin= g - just like linux kernel config file.? -DM On Friday, September 1, 2017, 5:55:51 AM PDT, Kyle Larose wrote: =20 =20 How is it failing? Is it dropping with a frame too long counter? Are you s= ure it's not dropping before your device? Have you made sure the max frame = size of every hop in between is large enough? -----Original Message----- From: users [mailto:users-bounces@dpdk.org] On Behalf Of Dharmesh Mehta Sent: Friday, September 01, 2017 2:10 AM To: users@dpdk.org Subject: [dpdk-users] jumbo frame support..(more than 1500 bytes) Sorry for resubmission, Still I am stuck at receiving any packet more than 1500+bytes. is it relate= d to driver?I can send packet larger than 1500bytes so I am not suspecting = anything wrong with my mbuf initialization. In my application I am using following code... #define MBUF_CACHE_SIZE 128#define MBUF_DATA_SIZE RTE_MBUF_DEFAULT_BUF_SIZE= #define JUMBO_FRAME_MAX_SIZE =C2=A0 =C2=A00x2600 //(9728 bytes) .rxmode =3D= { .mq_mode =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D ETH_MQ_RX_VMDQ_ONLY, .split_hdr_= size =3D 0, .header_split =C2=A0 =3D 0, /**< Header Split disabled */ .hw_i= p_checksum =3D 0, /**< IP checksum offload disabled */ .hw_vlan_filter =3D = 0, /**< VLAN filtering disabled */ .hw_vlan_strip =C2=A0=3D 1, /**< VLAN st= rip enabled. */ .jumbo_frame =C2=A0 =C2=A0=3D 1, /**< Jumbo Frame Support e= nabled */ .hw_strip_crc =C2=A0 =3D 1, /**< CRC stripped by hardware */ .ena= ble_scatter =3D 1, //required for jumbofram + 1500. .max_rx_pkt_len =3D JUM= BO_FRAME_MAX_SIZE,//ETHER_MAX_LEN }, create_mbuf_pool(valid_num_ports, rte_= lcore_count() - 1, MBUF_DATA_SIZE, MAX_QUEUES, RTE_TEST_RX_DESC_DEFAULT, MB= UF_CACHE_SIZE); I am also calling=C2=A0rte_eth_dev_set_mtu, to set MTU 9000, and verified w= ith=C2=A0rte_eth_dev_get_mtu. Below is my system info / logs from dpdk (17.05.1). Yours help is really appreciated. Thanks.DM. uname -aLinux 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017= x86_64 x86_64 x86_64 GNU/Linux modinfo uio_pci_genericfilename: =C2=A0 =C2= =A0 =C2=A0 /lib/modules/3.10.0-514.10.2.el7.x86_64/kernel/drivers/uio/uio_p= ci_generic.kodescription: =C2=A0 =C2=A0Generic UIO driver for PCI 2.3 devic= esauthor: =C2=A0 =C2=A0 =C2=A0 =C2=A0 Michael S. Tsirkin li= cense: =C2=A0 =C2=A0 =C2=A0 =C2=A0GPL v2version: =C2=A0 =C2=A0 =C2=A0 =C2= =A00.01.0rhelversion: =C2=A0 =C2=A07.3srcversion: =C2=A0 =C2=A0 10714380C20= 25655D980132depends: =C2=A0 =C2=A0 =C2=A0 =C2=A0uiointree: =C2=A0 =C2=A0 = =C2=A0 =C2=A0 Yvermagic: =C2=A0 =C2=A0 =C2=A0 3.10.0-514.10.2.el7.x86_64 SM= P mod_unload modversions=C2=A0signer: =C2=A0 =C2=A0 =C2=A0 =C2=A0 CentOS Li= nux kernel signing keysig_key: =C2=A0 =C2=A0 =C2=A0 =C2=A027:F2:04:85:EB:EB= :3B:2D:54:AD:D6:1E:57:B3:08:FA:E0:70:F4:1Fsig_hashalgo: =C2=A0 sha256 dpdk-17.05.1 $ ./bind2dpdk_status.sh=C2=A0Checking Ethernet port binding with DPDK Network devices using DPDK-compatible driver=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D0000:01:00.1 'I350 Gigabit Network Connection 15= 21' drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:01:00.2 'I350 Gigab= it Network Connection 1521' drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci= 0000:01:00.3 'I350 Gigabit Network Connection 1521' drv=3Duio_pci_generic u= nused=3Digb_uio,vfio-pci0000:03:00.0 'I350 Gigabit Network Connection 1521'= drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:03:00.1 'I350 Gigabit = Network Connection 1521' drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci000= 0:03:00.2 'I350 Gigabit Network Connection 1521' drv=3Duio_pci_generic unus= ed=3Digb_uio,vfio-pci0000:03:00.3 'I350 Gigabit Network Connection 1521' dr= v=3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:04:00.0 'I350 Gigabit Net= work Connection 1521' drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:0= 4:00.1 'I350 Gigabit Network Connection 1521' drv=3Duio_pci_generic unused= =3Digb_uio,vfio-pci0000:04:00.2 'I350 Gigabit Network Connection 1521' drv= =3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:04:00.3 'I350 Gigabit Netw= ork Connection 1521' drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:05= :00.0 'I350 Gigabit Network Connection 1521' drv=3Duio_pci_generic unused= =3Digb_uio,vfio-pci0000:05:00.1 'I350 Gigabit Network Connection 1521' drv= =3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:05:00.2 'I350 Gigabit Netw= ork Connection 1521' drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:05= :00.3 'I350 Gigabit Network Connection 1521' drv=3Duio_pci_generic unused= =3Digb_uio,vfio-pci0000:82:00.0 'I350 Gigabit Network Connection 1521' drv= =3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:82:00.1 'I350 Gigabit Netw= ork Connection 1521' drv=3Duio_pci_generic unused=3Digb_uio,vfio-pci0000:82= :00.2 'I350 Gigabit Network Connection 1521' drv=3Duio_pci_generic unused= =3Digb_uio,vfio-pci0000:82:00.3 'I350 Gigabit Network Connection 1521' drv= =3Duio_pci_generic unused=3Digb_uio,vfio-pci Network devices using kernel d= river=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D0000:01:00.0 'I350 Gigabit Network Conn= ection 1521' if=3Deth0 drv=3Digb unused=3Digb_uio,vfio-pci,uio_pci_generic Other Network devices=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Crypto devices using DPDK-compatible driver=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D Crypto devices using kernel driver=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Other Crypto devices=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D Eventdev devices using DPDK-compatible driver=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Eventdev devices using kernel driver=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Other Eventdev devices=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Mempool devices using DPDK-compatible driver=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D Mempool devices using kernel driver=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Other Mempool devices=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D EAL: Detected 72 lcore(s)EAL: Auto-detected process type: PRIMARYEAL: Probi= ng VFIO support...EAL: VFIO support initializedEAL: PCI device 0000:01:00.0= on NUMA socket 0EAL: =C2=A0 probe driver: 8086:1521 net_e1000_igbEAL: PCI = device 0000:01:00.1 on NUMA socket 0EAL: =C2=A0 Device is blacklisted, not = initializingEAL: PCI device 0000:01:00.2 on NUMA socket 0EAL: =C2=A0 Device= is blacklisted, not initializingEAL: PCI device 0000:01:00.3 on NUMA socke= t 0EAL: =C2=A0 Device is blacklisted, not initializingEAL: PCI device 0000:= 03:00.0 on NUMA socket 0EAL: =C2=A0 probe driver: 8086:1521 net_e1000_igbEA= L: PCI device 0000:03:00.1 on NUMA socket 0EAL: =C2=A0 Device is blackliste= d, not initializingEAL: PCI device 0000:03:00.2 on NUMA socket 0EAL: =C2=A0= Device is blacklisted, not initializingEAL: PCI device 0000:03:00.3 on NUM= A socket 0EAL: =C2=A0 Device is blacklisted, not initializingEAL: PCI devic= e 0000:04:00.0 on NUMA socket 0EAL: =C2=A0 Device is blacklisted, not initi= alizingEAL: PCI device 0000:04:00.1 on NUMA socket 0EAL: =C2=A0 Device is b= lacklisted, not initializingEAL: PCI device 0000:04:00.2 on NUMA socket 0EA= L: =C2=A0 Device is blacklisted, not initializingEAL: PCI device 0000:04:00= .3 on NUMA socket 0EAL: =C2=A0 Device is blacklisted, not initializingEAL: = PCI device 0000:05:00.0 on NUMA socket 0EAL: =C2=A0 Device is blacklisted, = not initializingEAL: PCI device 0000:05:00.1 on NUMA socket 0EAL: =C2=A0 De= vice is blacklisted, not initializingEAL: PCI device 0000:05:00.2 on NUMA s= ocket 0EAL: =C2=A0 Device is blacklisted, not initializingEAL: PCI device 0= 000:05:00.3 on NUMA socket 0EAL: =C2=A0 Device is blacklisted, not initiali= zingEAL: PCI device 0000:82:00.0 on NUMA socket 1EAL: =C2=A0 Device is blac= klisted, not initializingEAL: PCI device 0000:82:00.1 on NUMA socket 1EAL: = =C2=A0 Device is blacklisted, not initializingEAL: PCI device 0000:82:00.2 = on NUMA socket 1EAL: =C2=A0 Device is blacklisted, not initializingEAL: PCI= device 0000:82:00.3 on NUMA socket 1EAL: =C2=A0 Device is blacklisted, not= initializingnb_ports=3D1valid_num_ports=3D1MBUF_DATA_SIZE=3D2176 , MAX_QUE= UES=3D8, RTE_TEST_RX_DESC_DEFAULT=3D1024 , MBUF_CACHE_SIZE=3D128Waiting for= data...portid=3D0enabled_port_mask=3D1**** MTU is programmed successfully = to 9000port_init port - 0=C2=A0Device supports maximum rx queues are 8MAX_Q= UEUES defined as 8max_no_tx_queue =3D 8 , max_no_rx_queue =3D 8pf queue num= : 0, configured vmdq pool num: 8, each vmdq pool has 1 queuesport=3D0,rx_ri= ngs=3D8,tx_rings=3D3rx-queue setup successfully q=3D0rx-queue setup success= fully q=3D1rx-queue setup successfully q=3D2rx-queue setup successfully q= =3D3rx-queue setup successfully q=3D4rx-queue setup successfully q=3D5rx-qu= eue setup successfully q=3D6rx-queue setup successfully q=3D7tx-queue setup= successfully q=3D0tx-queue setup successfully q=3D1tx-queue setup successf= ully q=3D2Port 0: Enabling HW FCVHOST_PORT: Max virtio devices supported: 8= VHOST_PORT: Port 0 MAC: a0 36 9f cb ba 34Dump Flow Control 0HighWater Martk= =3D33828LowWater Martk=3D32328PauseTime=3D1664Send XON Martk=3D1Mode=3D1MAC= Control Frame forward=3D0Setting Flow Control =3D FULLDump Flow Control 0H= ighWater Martk=3D33828LowWater Martk=3D32328PauseTime=3D1664Send XON Martk= =3D1Mode=3D1MAC Control Frame forward=3D0**** MTU is programmed successfull= y to 9000VHOST_DATA: ********************* TX - Procesing on Core 40 starte= d********************* TX - Procesing on Core 40 startedVHOST_DATA: *******= ********** RX Procesing on Core 41 started***************** RX Procesing on= Core 41 startedvmdq_conf_default.rxmode.mq_mode=3D4vmdq_conf_default.rxmod= e.max_rx_pkt_len=3D9728vmdq_conf_default.rxmode.split_hdr_size=3D0vmdq_conf= _default.rxmode.header_split=3D0vmdq_conf_default.rxmode.hw_ip_checksum=3D0= vmdq_conf_default.rxmode.hw_vlan_filter=3D0vmdq_conf_default.rxmode.hw_vlan= _strip=3D1vmdq_conf_default.rxmode.hw_vlan_extend=3D0vmdq_conf_default.rxmo= de.jumbo_frame=3D1vmdq_conf_default.rxmode.hw_strip_crc=3D1vmdq_conf_defaul= t.rxmode.enable_scatter=3D1vmdq_conf_default.rxmode.enable_lro=3D0VHOST_CON= FIG: vhost-user server: socket created, fd: 23VHOST_CONFIG: bind to /tmp/vu= br0 =20 >From cpaquin@redhat.com Fri Sep 1 17:59:30 2017 Return-Path: Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by dpdk.org (Postfix) with ESMTP id 557D5325A for ; Fri, 1 Sep 2017 17:59:30 +0200 (CEST) Received: by mail-oi0-f50.google.com with SMTP id r203so5359976oih.0 for ; Fri, 01 Sep 2017 08:59:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=go/1mmwfV9Ha5EmAshoxnnF7VNw8RKFyVdygav9VJgc=; b=eHSrzr4Oe6Vlk/GFyrOYiRwrt4so24Uw2/LsiMhmdupa65IPMOseet/MixRjwm6HYr sad26hXwxPGZHDZsNR19xcD3Nav39iU4aO8Y3Jz/XkvoqAjFcEMwQeJGNsHrwqkJCM8d Pvcw51K7ivpPO2fgwQ+aQuu1mvxk9Q4VUKhUsTOd4yz3zrVZgR0IqBPoPEPRjWI1NcPk 813T7MPaOo1bDRUNscY+NC3wwdmokvboAQni/UDXvF/3YssQJtFlf2saH6OC868FHPCK Lw8Z9YfdZmAACiAq0WEjCm7JPeaph4jE7wiN1AgGNDdakzxI241S2Z8F2wTqbcc+wYhn aWpA== X-Gm-Message-State: AHPjjUgLlb1Rn7xRdFX6uael6hmjxfsqyJpVv+gfiAd1Yk8i/dn5VkKe 8MxDdNRg2RsEgKMiftQyBuvLFH6WTMVM7JOShA== X-Google-Smtp-Source: ADKCNb47KU20DnM53349Ej3pt+bOF9pBj+5XXNAytI2oKYrj3fFNhwTslsV7i52qNyhnyeIx+xgSo+cFIwhaCdI0h24= X-Received: by 10.202.85.19 with SMTP id j19mr2385880oib.193.1504281569376; Fri, 01 Sep 2017 08:59:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.150.195 with HTTP; Fri, 1 Sep 2017 08:59:08 -0700 (PDT) In-Reply-To: <1577249268.1093678.1504281150569@mail.yahoo.com> References: <800120698.826966.1504246225460.ref@mail.yahoo.com> <800120698.826966.1504246225460@mail.yahoo.com> <1577249268.1093678.1504281150569@mail.yahoo.com> From: Chris Paquin Date: Fri, 1 Sep 2017 11:59:08 -0400 Message-ID: To: Dharmesh Mehta Cc: "users@dpdk.org" , Kyle Larose Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] jumbo frame support..(more than 1500 bytes) X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2017 15:59:30 -0000 Darmesh I use the command below to show dropped packets. Not sure if this helps testpmd> show port stats 0 ######################## NIC statistics for port 0 ######################## RX-packets: 0 RX-missed: 0 RX-bytes: 0 RX-errors: 0 RX-nombuf: 2366029984 TX-packets: 0 TX-errors: 0 TX-bytes: 0 Throughput (since last show) Rx-pps: 0 Tx-pps: 0 ############################################################################ CHRISTOPHER PAQUIN SENIOR CLOUD CONSULTANT, RHCE, RHCSA-OSP Red Hat M: 770-906-7646 On Fri, Sep 1, 2017 at 11:52 AM, Dharmesh Mehta wrote: > Hello Kyle, > Could you please tell me which DEBUG flag I should turn on it can print > error. > how do I check it is not dropping before my device? > Have you made sure the max frame size of every hop in between is large > enough? > - can you tell me which file / debug flag I should turn on so I get > more insight. > > > thanks,dharmesh.If you see my e-mail. setting of buffer size is done > correctly in my main application. > I hope same #define will be get picked by lib / driver etc.... during > compilation. > Do we have centralized place in DPDK where we can configure all this > setting - just like linux kernel config file.? > -DM > On Friday, September 1, 2017, 5:55:51 AM PDT, Kyle Larose < > klarose@sandvine.com> wrote: > > How is it failing? Is it dropping with a frame too long counter? Are you > sure it's not dropping before your device? Have you made sure the max frame > size of every hop in between is large enough? > > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Dharmesh Mehta > Sent: Friday, September 01, 2017 2:10 AM > To: users@dpdk.org > Subject: [dpdk-users] jumbo frame support..(more than 1500 bytes) > > Sorry for resubmission, > Still I am stuck at receiving any packet more than 1500+bytes. is it > related to driver?I can send packet larger than 1500bytes so I am not > suspecting anything wrong with my mbuf initialization. > > In my application I am using following code... > #define MBUF_CACHE_SIZE 128#define MBUF_DATA_SIZE > RTE_MBUF_DEFAULT_BUF_SIZE#define JUMBO_FRAME_MAX_SIZE 0x2600 //(9728 > bytes) .rxmode = { .mq_mode = ETH_MQ_RX_VMDQ_ONLY, .split_hdr_size = > 0, .header_split = 0, /**< Header Split disabled */ .hw_ip_checksum = 0, > /**< IP checksum offload disabled */ .hw_vlan_filter = 0, /**< VLAN > filtering disabled */ .hw_vlan_strip = 1, /**< VLAN strip enabled. */ > .jumbo_frame = 1, /**< Jumbo Frame Support enabled */ .hw_strip_crc = > 1, /**< CRC stripped by hardware */ .enable_scatter = 1, //required for > jumbofram + 1500. .max_rx_pkt_len = JUMBO_FRAME_MAX_SIZE,//ETHER_MAX_LEN > }, create_mbuf_pool(valid_num_ports, rte_lcore_count() - 1, > MBUF_DATA_SIZE, MAX_QUEUES, RTE_TEST_RX_DESC_DEFAULT, MBUF_CACHE_SIZE); > > I am also calling rte_eth_dev_set_mtu, to set MTU 9000, and verified > with rte_eth_dev_get_mtu. > Below is my system info / logs from dpdk (17.05.1). > Yours help is really appreciated. > > Thanks.DM. > uname -aLinux 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC > 2017 x86_64 x86_64 x86_64 GNU/Linux modinfo uio_pci_genericfilename: > /lib/modules/3.10.0-514.10.2.el7.x86_64/kernel/drivers/uio/uio_pci_generic.kodescription: > Generic UIO driver for PCI 2.3 devicesauthor: Michael S. Tsirkin > license: GPL v2version: 0.01.0rhelversion: > 7.3srcversion: 10714380C2025655D980132depends: uiointree: > Yvermagic: 3.10.0-514.10.2.el7.x86_64 SMP mod_unload > modversions signer: CentOS Linux kernel signing keysig_key: > 27:F2:04:85:EB:EB:3B:2D:54:AD:D6:1E:57:B3:08:FA:E0:70:F4:1Fsig_hashalgo: > sha256 > dpdk-17.05.1 > $ ./bind2dpdk_status.sh Checking Ethernet port binding with DPDK > > Network devices using DPDK-compatible driver======================== > ====================0000:01:00.1 'I350 Gigabit Network Connection 1521' > drv=uio_pci_generic unused=igb_uio,vfio-pci0000:01:00.2 'I350 Gigabit > Network Connection 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:01:00.3 > 'I350 Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:03:00.0 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:03:00.1 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:03:00.2 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:03:00.3 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:04:00.0 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:04:00.1 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:04:00.2 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:04:00.3 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:05:00.0 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:05:00.1 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:05:00.2 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:05:00.3 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:82:00.0 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:82:00.1 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci0000:82:00.2 'I350 Gigabit Network Connection > 1521' drv=uio_pci_generic unused=igb_uio,vfio-pci0000:82:00.3 'I350 > Gigabit Network Connection 1521' drv=uio_pci_generic > unused=igb_uio,vfio-pci Network devices using kernel > driver===================================0000:01:00.0 'I350 Gigabit > Network Connection 1521' if=eth0 drv=igb unused=igb_uio,vfio-pci,uio_ > pci_generic > Other Network devices===================== > Crypto devices using DPDK-compatible driver======================== > =================== > Crypto devices using kernel driver================================== > Other Crypto devices==================== Eventdev devices using > DPDK-compatible driver============================================= > Eventdev devices using kernel driver======================== > ============ > Other Eventdev devices====================== > Mempool devices using DPDK-compatible driver======================== > ==================== > Mempool devices using kernel driver======================== > =========== > Other Mempool devices===================== > > > > EAL: Detected 72 lcore(s)EAL: Auto-detected process type: PRIMARYEAL: > Probing VFIO support...EAL: VFIO support initializedEAL: PCI device > 0000:01:00.0 on NUMA socket 0EAL: probe driver: 8086:1521 > net_e1000_igbEAL: PCI device 0000:01:00.1 on NUMA socket 0EAL: Device is > blacklisted, not initializingEAL: PCI device 0000:01:00.2 on NUMA socket > 0EAL: Device is blacklisted, not initializingEAL: PCI device 0000:01:00.3 > on NUMA socket 0EAL: Device is blacklisted, not initializingEAL: PCI > device 0000:03:00.0 on NUMA socket 0EAL: probe driver: 8086:1521 > net_e1000_igbEAL: PCI device 0000:03:00.1 on NUMA socket 0EAL: Device is > blacklisted, not initializingEAL: PCI device 0000:03:00.2 on NUMA socket > 0EAL: Device is blacklisted, not initializingEAL: PCI device 0000:03:00.3 > on NUMA socket 0EAL: Device is blacklisted, not initializingEAL: PCI > device 0000:04:00.0 on NUMA socket 0EAL: Device is blacklisted, not > initializingEAL: PCI device 0000:04:00.1 on NUMA socket 0EAL: Device is > blacklisted, not initializingEAL: PCI device 0000:04:00.2 on NUMA socket > 0EAL: Device is blacklisted, not initializingEAL: PCI device 0000:04:00.3 > on NUMA socket 0EAL: Device is blacklisted, not initializingEAL: PCI > device 0000:05:00.0 on NUMA socket 0EAL: Device is blacklisted, not > initializingEAL: PCI device 0000:05:00.1 on NUMA socket 0EAL: Device is > blacklisted, not initializingEAL: PCI device 0000:05:00.2 on NUMA socket > 0EAL: Device is blacklisted, not initializingEAL: PCI device 0000:05:00.3 > on NUMA socket 0EAL: Device is blacklisted, not initializingEAL: PCI > device 0000:82:00.0 on NUMA socket 1EAL: Device is blacklisted, not > initializingEAL: PCI device 0000:82:00.1 on NUMA socket 1EAL: Device is > blacklisted, not initializingEAL: PCI device 0000:82:00.2 on NUMA socket > 1EAL: Device is blacklisted, not initializingEAL: PCI device 0000:82:00.3 > on NUMA socket 1EAL: Device is blacklisted, not > initializingnb_ports=1valid_num_ports=1MBUF_DATA_SIZE=2176 , > MAX_QUEUES=8, RTE_TEST_RX_DESC_DEFAULT=1024 , MBUF_CACHE_SIZE=128Waiting > for data...portid=0enabled_port_mask=1**** MTU is programmed successfully > to 9000port_init port - 0 Device supports maximum rx queues are 8MAX_QUEUES > defined as 8max_no_tx_queue = 8 , max_no_rx_queue = 8pf queue num: 0, > configured vmdq pool num: 8, each vmdq pool has 1 > queuesport=0,rx_rings=8,tx_rings=3rx-queue setup successfully q=0rx-queue > setup successfully q=1rx-queue setup successfully q=2rx-queue setup > successfully q=3rx-queue setup successfully q=4rx-queue setup successfully > q=5rx-queue setup successfully q=6rx-queue setup successfully q=7tx-queue > setup successfully q=0tx-queue setup successfully q=1tx-queue setup > successfully q=2Port 0: Enabling HW FCVHOST_PORT: Max virtio devices > supported: 8VHOST_PORT: Port 0 MAC: a0 36 9f cb ba 34Dump Flow Control > 0HighWater Martk=33828LowWater Martk=32328PauseTime=1664Send XON > Martk=1Mode=1MAC Control Frame forward=0Setting Flow Control = FULLDump > Flow Control 0HighWater Martk=33828LowWater Martk=32328PauseTime=1664Send > XON Martk=1Mode=1MAC Control Frame forward=0**** MTU is programmed > successfully to 9000VHOST_DATA: ********************* TX - Procesing on > Core 40 started********************* TX - Procesing on Core 40 > startedVHOST_DATA: ***************** RX Procesing on Core 41 > started***************** RX Procesing on Core 41 startedvmdq_conf_default. > rxmode.mq_mode=4vmdq_conf_default.rxmode.max_rx_pkt_len= > 9728vmdq_conf_default.rxmode.split_hdr_size=0vmdq_conf_ > default.rxmode.header_split=0vmdq_conf_default.rxmode.hw_ > ip_checksum=0vmdq_conf_default.rxmode.hw_vlan_filter= > 0vmdq_conf_default.rxmode.hw_vlan_strip=1vmdq_conf_default. > rxmode.hw_vlan_extend=0vmdq_conf_default.rxmode.jumbo_ > frame=1vmdq_conf_default.rxmode.hw_strip_crc=1vmdq_ > conf_default.rxmode.enable_scatter=1vmdq_conf_default. > rxmode.enable_lro=0VHOST_CONFIG: vhost-user server: socket created, fd: > 23VHOST_CONFIG: bind to /tmp/vubr0 > > >