From: Harold Huang <baymaxhuang@gmail.com>
To: baymaxhuang@gmail.com
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [PATCH v4] net/kni: reset rte_kni_conf struct before initialization
Date: Thu, 23 Dec 2021 11:01:55 +0800 [thread overview]
Message-ID: <CAHJXk3YVRLQ4j2TP3M_+YQ4yDetzVS2cNQCUzuNvGXEEtLE1Gg@mail.gmail.com> (raw)
The problem this patch wants to solve can be reproduced by ovs-dpdk:
1. create a kni port in ovs:
ovs-vsctl add-port ovs-br0 kni0 -- set Interface kni0 type=dpdk
options:dpdk-devargs=net_kni0
2. change the mtu of the kni device in kernel:
ip link set kni0 mtu 1500
If we do not set rte_kni_conf to 0, the min_mtu and max_mtu are random
and change mtu could be failed.
next reply other threads:[~2021-12-23 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 3:01 Harold Huang [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 7:24 [PATCH] " Harold Huang
2021-12-05 6:21 ` [PATCH v4] " Harold Huang
2022-02-27 20:12 ` Thomas Monjalon
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=CAHJXk3YVRLQ4j2TP3M_+YQ4yDetzVS2cNQCUzuNvGXEEtLE1Gg@mail.gmail.com \
--to=baymaxhuang@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).