From: Igor Ryzhov <iryzhov@nfware.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] kni: add ability to set min/max MTU
Date: Sun, 27 Oct 2019 22:56:14 +0300 [thread overview]
Message-ID: <CAF+s_Fygb0GjRRyNzs5j1GwvqCBAhKpOUSUBg18jiKdRAFMaeA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ziZ0x70zc+Cf5R=tjfhBweayGgpNUp+FOk5S2G_Sh5pw@mail.gmail.com>
Hi David, Ferruh,
Sorry I was on vacation. Thank you for dealing with this.
Best regards,
Igor
On Sun, Oct 27, 2019 at 1:12 PM David Marchand <david.marchand@redhat.com>
wrote:
> On Fri, Oct 25, 2019 at 8:31 PM Ferruh Yigit <ferruh.yigit@intel.com>
> wrote:
> >
> > From: Igor Ryzhov <iryzhov@nfware.com>
> >
> > Starting with kernel version 4.10, there are new min/max MTU values in
> > net_device structure, which are set to ETH_MIN_MTU and ETH_DATA_LEN by
> > default. We should be able to change these values to allow MTU more than
> > 1500 to be set on KNI.
> >
> > Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
> > Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Applied, thanks.
>
>
> --
> David Marchand
>
>
prev parent reply other threads:[~2019-10-27 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 11:22 [dpdk-dev] [PATCH] " Igor Ryzhov
2019-10-11 16:16 ` Ferruh Yigit
2019-10-16 6:40 ` David Marchand
2019-10-16 10:43 ` Ferruh Yigit
2019-10-16 10:55 ` David Marchand
2019-10-16 14:47 ` David Marchand
2019-10-16 14:59 ` Ferruh Yigit
2019-10-25 18:30 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2019-10-25 18:32 ` Ferruh Yigit
2019-10-27 10:12 ` David Marchand
2019-10-27 19:56 ` Igor Ryzhov [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=CAF+s_Fygb0GjRRyNzs5j1GwvqCBAhKpOUSUBg18jiKdRAFMaeA@mail.gmail.com \
--to=iryzhov@nfware.com \
--cc=david.marchand@redhat.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).