From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Liron Himi <lironh@marvell.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] KNI jumbo support
Date: Wed, 2 Jan 2019 10:27:51 +0000 [thread overview]
Message-ID: <7f4a99da-bf54-59b7-7d35-5898592874f2@intel.com> (raw)
In-Reply-To: <SN1PR18MB0448800C7F1C6F94DB452574C6BF0@SN1PR18MB0448.namprd18.prod.outlook.com>
On 12/20/2018 3:27 PM, Liron Himi wrote:
> Hi,
>
> I'm using DPDK18.11, and I launch a KNI flow.
> We need to pass jumbo frames via KNI interface but when we try to change its MTU (using ifconfig) above 1500 we get an error.
>
> is it possible?
> I noticed that the 'rte_kni' support some network callbacks (e.g. changing MTU) but the rte_eth_kni doesn't define them.
> Is it possible to define them from outside? i.e. part of application code.
Hi Liron,
KNI PMD is not using callbacks right now, you can have them if you use kni
library directly, as kni sample application does.
And as far as I remember someone pointed in the list previously that in kernel
side, for Rx mbuf segmentation is implemented but for Tx it is not. So if kni
interface tries to send a packet which is greater than mbuf size, it will be
dropped, you may need to implement that part as well.
Regards,
ferruh
prev parent reply other threads:[~2019-01-02 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 15:27 Liron Himi
2018-12-21 0:48 ` [dpdk-users] How to show debug log in DPDK and DPDK application Hideyuki Yamashita
2018-12-21 3:10 ` Stephen Hemminger
2018-12-21 6:42 ` Hideyuki Yamashita
2019-01-02 10:27 ` 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=7f4a99da-bf54-59b7-7d35-5898592874f2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=lironh@marvell.com \
--cc=users@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).