DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Deshvanth Mirle Jayaprakash (dmirleja)" <dmirleja@cisco.com>
To: "Zhang, Helin" <helin.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Issues running Ethtool on KNI interfaces
Date: Mon, 13 Oct 2014 07:39:27 +0000	[thread overview]
Message-ID: <D060CEE2.1189F%dmirleja@cisco.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A79B8F1@SHSMSX104.ccr.corp.intel.com>

Thanks Helin, have been trying this for some time, Is there any other way
I can pass IOCTLs to IGB-UIO interfaces. Can I use /dev/uio0 and /dev/uio1
? Can I use IOCTLS on these references in Kernel to gather interface
statistics, set MTU or bring up/down UIO interfaces.

/Desh

On 10/13/14 12:34 AM, "Zhang, Helin" <helin.zhang@intel.com> wrote:

>Hi Desh
>
>You tried to use ethtool for KNI interfaces in VM, right? I don't think
>it is supported in VM.
>Currently it just supports ethtool for KNI interfaces in host for some
>igb and ixgbe NICs.
>
>Regards,
>Helin
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Deshvanth Mirle
>> Jayaprakash (dmirleja)
>> Sent: Monday, October 13, 2014 3:21 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] Issues running Ethtool on KNI interfaces
>> 
>> Hi,
>> 
>> Hypervisor: KVM
>> 
>> VM: Linux OS with 2.6.32 Kernel
>> 
>> VM Settings:
>> 
>> 8 vCPUs, 8192 MB of memory, CPU Configuration: Copy Host CPU Config
>> (SandyBridge), Manually set CPU topology: Sockets=2, Cores=4, Threads=1
>> 
>> 10Gigi Passthrough Interfaces attached to VM: Intel X520
>> 
>> 
>> DPDK settings:
>> 
>> 
>> DPDK Version: 1.6R2
>> 
>> 
>> echo 512 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
>> 
>> rmmod ixgbe
>> 
>> insmod igb_uio.ko
>> 
>> mkdir /mnt/hugepages
>> 
>> mount -t hugetlbfs nodev /mnt/hugepages
>> 
>> #./igb_uio_bind.py --status
>> 
>> #./igb_uio_bind.py --bind=igb_uio 03:01.0
>> 
>> #./igb_uio_bind.py --bind=igb_uio 03:02.0
>> 
>> #./igb_uio_bind.py --status
>> 
>> modprobe hwmon
>> 
>> insmod rte_kni.ko
>> 
>> ./kni -c 0x1E -n 2 --socket-mem 512 -- -p 0x3
>>--config="(0,1,3),(1,2,4)" &
>> 
>> 
>> Having KNI process running in the background, creates two KNI interfaces
>> called vEth0 and vEth1 which corresponds to IGB-UIO interfaces attached
>>to
>> the Userspace. The issue is that the Ethtool doesn't work with KNI
>>interfaces.
>> Is there anything that I am missing, How can I get Ethtool to work with
>>KNI
>> interfaces? Also, If I do not use --socket-mem OR -m EAL option, KNI
>>application
>> consumes all the huge pages(It doesn't mater 512/4096) assigned in the
>>very
>> first step.Is that expected behavior? Can I get KNI to work without
>>assigning
>> any Hugepages?
>> 
>> 
>> 
>> Also, I have attached screen shots of KNI log file. Please take a look.
>> 
>> 
>> Thanks,
>> 
>> Desh

  reply	other threads:[~2014-10-13  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13  7:21 Deshvanth Mirle Jayaprakash (dmirleja)
2014-10-13  7:34 ` Zhang, Helin
2014-10-13  7:39   ` Deshvanth Mirle Jayaprakash (dmirleja) [this message]
2014-10-13  7:46     ` Zhang, Helin
2014-10-17  7:58       ` Deshvanth Mirle Jayaprakash (dmirleja)
2014-10-17  8:12         ` Zhang, Helin

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=D060CEE2.1189F%dmirleja@cisco.com \
    --to=dmirleja@cisco.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@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).