From: "Tim Deng" <dpdkdev@126.com>
To: "Zhou, Danny" <danny.zhou@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Manage DPDK port capability via KNI
Date: Wed, 25 Feb 2015 17:55:57 +0800 (CST) [thread overview]
Message-ID: <9da2437.5fd7.14bc02a1013.Coremail.dpdkdev@126.com> (raw)
In-Reply-To: <DFDF335405C17848924A094BC35766CF0AABBCFE@SHSMSX104.ccr.corp.intel.com>
Thanks Danny,
That means DPDK ports have to have dedicated control path other than KNI.
I originally got confused by the statement at http://dpdk.org/doc/guides/prog_guide/kernel_nic_interface.html:
"...Allows management of DPDK ports using standard Linux net tools such as ethtool, ifconfig and tcpdump."
Thanks,
Tim
At 2015-02-25 13:05:08, "Zhou, Danny" <danny.zhou@intel.com> wrote:
>You can do it but it will not sync with DPDK. In current KNI implementation, the devices'
>I/O address spaces are mapped to both userspace DPDK and kenrelspace KNI, so one
>can control the NIC device independently(using ethtool for KNI and ethdev APIs for DPDK)
>without synchronization.
>
>In theory, KNI should route all device control request from ethtool to DPDK. But unfortunately,
>a short path is adopted at the moment due to DPDK reused lots of legacy kernel codes with BSD license.
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tim Deng
>> Sent: Wednesday, February 25, 2015 9:57 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] Manage DPDK port capability via KNI
>>
>> Hi,
>>
>>
>> I am wondering how could we manage a DPDK port offload capabilities,
>> e.g. if we want to disable TSO capability on a DPDK port, is it feasible
>> that we use ethtool to configure a KNI then the config will be sync to a DPDK port?
>>
>>
>> Thanks,
>> Tim
prev parent reply other threads:[~2015-02-25 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 1:56 Tim Deng
2015-02-25 5:05 ` Zhou, Danny
2015-02-25 9:55 ` Tim Deng [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=9da2437.5fd7.14bc02a1013.Coremail.dpdkdev@126.com \
--to=dpdkdev@126.com \
--cc=danny.zhou@intel.com \
--cc=dev@dpdk.org \
/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).