From: "Zhou, Danny" <danny.zhou@intel.com>
To: Harish Patil <harish.patil@qlogic.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI ethtool related question
Date: Fri, 10 Oct 2014 23:14:36 +0000 [thread overview]
Message-ID: <DFDF335405C17848924A094BC35766CF0A957A1F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <036FA1BC4A80D448AB7D9C3AAFBBCAF59F83CC3E@AVMB1.qlogic.org>
Yes, it is doable. The KNI establishes software based request/response queues between
vNIC device in kernel and PMD in user space. So all ethtool commands will be interpreted by
KNI driver and forwarded to PMD which really configure NIC registers.
Basically, it is the only option. Or you have to call DPDK APIs to configure NIC in user space.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Harish Patil
> Sent: Saturday, October 11, 2014 2:32 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] KNI ethtool related question
>
> Hello,
> I would like to use KNI interface *only* for the ethtool/ifconfig support,
> not for the data packets movement into and from the kernel. For the fast
> path, I would like to use PMD. Is this doable? What are the other options
> for a PMD driver to support standard linux utilities?
> Thanks in adv.,
> Harish
>
>
>
> ________________________________
>
> This message and any attached documents contain information from the sending company or its parent company(s), subsidiaries,
> divisions or branch offices that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this
> information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this
> message.
prev parent reply other threads:[~2014-10-10 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 18:32 Harish Patil
2014-10-10 23:14 ` Zhou, Danny [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=DFDF335405C17848924A094BC35766CF0A957A1F@SHSMSX104.ccr.corp.intel.com \
--to=danny.zhou@intel.com \
--cc=dev@dpdk.org \
--cc=harish.patil@qlogic.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).