From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yasuhiro Ohara <yasu@nttv6.jp>, dev@dpdk.org
Subject: Re: [dpdk-dev] KNI PCIe number and VLAN Stripping
Date: Tue, 20 Mar 2018 13:56:23 +0000 [thread overview]
Message-ID: <ed1a9b96-44e5-624a-9279-52d2f12f81d4@intel.com> (raw)
In-Reply-To: <20180319.101041.604023037230225350.yasu@nttv6.jp>
On 3/19/2018 1:10 AM, Yasuhiro Ohara wrote:
>
> Hi.
>
> It is much appreciated if someone could answer the following questions.
>
> 1. Regarding KNI, what is the reasoning of giving the PCI device
> number information when setting kni I/F ? Can the data be blank or
> dummy ? I would like to create a virtual I/F inside my application
> and its corresponding kni, which may not have the corresponding
> physical PCIe slot.
For KNI pci address information is for ethtool support [1] and it can be blank,
for example KNI PMD uses it blank.
[1]
ethtool support is only for igb and ixgbe only. And this support is by default
disabled in config, need to enable CONFIG_RTE_KNI_KMOD_ETHTOOL config option for it.
>
> 2. the ETHER/VLAN/ARP packet looks not-supported both
> in mbuf_ptype(RTE_PTYPE_XXX in m->packet_type) and
> in PKT_RX_VLAN_STRIPPED situation.
> 2a. How can we encode in m->packet_type to indicate there are
> arp_hdr after the (ether_hdr,vlan_hdr) pair ?
> 2b. How can we get the next header value (i.e. ether_proto in
> vlan_hdr) when the vlan_hdr is stripped by the NIC ?
>
> Thanks in advance.
>
> Best regards,
> Yasu
>
prev parent reply other threads:[~2018-03-20 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 1:10 Yasuhiro Ohara
2018-03-20 13:56 ` Ferruh Yigit [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=ed1a9b96-44e5-624a-9279-52d2f12f81d4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=yasu@nttv6.jp \
/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).