From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Mallesh Koujalagi <malleshx.koujalagi@intel.com>, dev@dpdk.org
Cc: mtetsuyah@gmail.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix MTU setup error
Date: Wed, 31 Jan 2018 18:38:15 +0000 [thread overview]
Message-ID: <28c0162c-08be-008f-f3b7-2352b16c980d@intel.com> (raw)
In-Reply-To: <a51d3768-9ed9-d911-bb33-e5cebd92e800@intel.com>
On 1/31/2018 6:34 PM, Ferruh Yigit wrote:
> On 1/31/2018 2:08 AM, Mallesh Koujalagi wrote:
>
> net/null: support MTU update
>
>> NULL device is failed to attach ovs, reported operation not supported
>> and configuration failed.
>>
>> To attach ovs:
>> $VSCTL add-port ovs-br dpdk1 -- set Interface dpdk1 type=dpdk \
>> options:dpdk-devargs=eth_null0,size=64,copy=1
>>
>> Signed-off-by: Mallesh Koujalagi <malleshx.koujalagi@intel.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-01-31 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 2:08 Mallesh Koujalagi
2018-01-31 18:34 ` Ferruh Yigit
2018-01-31 18:38 ` 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=28c0162c-08be-008f-f3b7-2352b16c980d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=malleshx.koujalagi@intel.com \
--cc=mtetsuyah@gmail.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).