From: Liron Himi <lironh@marvell.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, Alan Winkowski <walan@marvell.com>,
Liron Himi <lironh@marvell.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v3] net/kni: calc mbuf&mtu according to given mb_pool
Date: Sun, 24 Mar 2019 10:05:29 +0000 [thread overview]
Message-ID: <MN2PR18MB23981CEC3FD9991B0CD38041C65D0@MN2PR18MB2398.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAHLOa7Q8D0wtkXG4MLa9gM0889JGDok-56nftHB=NDU7PxHOYg@mail.gmail.com>
Fixed. thanks
From: Rami Rosen <ramirose@gmail.com>
Sent: Saturday, March 23, 2019 23:49
To: Liron Himi <lironh@marvell.com>
Cc: ferruh.yigit@intel.com; dev@dpdk.org; Alan Winkowski <walan@marvell.com>
Subject: [EXT] Re: [dpdk-dev] [PATCH v3] net/kni: calc mbuf&mtu according to given mb_pool
External Email
________________________________
<lironh@marvell.com<mailto:lironh@marvell.com>>:
From: Liron Himi <lironh@marvell.com<mailto:lironh@marvell.com>>
- mbuf_size and mtu are now being calculated according
to the given mb-pool.
- max_mtu is now being set according to the given mtu
the above two changes provide the ability to work with jumbo frames
Signed-off-by: Liron Himi <lironh@marvell.com<mailto:lironh@marvell.com>>
Minors:
without it-> Without it
th given-> the given
if the bm-pool -> if the mb-pool
+* **Updated KNI kernel module, KNI PMD driver.**
+
+ Updated the KNI kernel module to set the max_mtu according to the given
+ initial mtu size. without it, the maximum mtu was 1500.
+
+ Updated the KNI PMD driver to set the mbuf_size and mtu based on
+ th given mb-pool. This provide the ability to pass jumbo frames
+ if the bm-pool contains suitable buffers' size.
+
Reviewd-by: Rami Rosen <ramirose@gmail.com<mailto:ramirose@gmail.com>>
next prev parent reply other threads:[~2019-03-24 10:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 8:47 [dpdk-dev] [PATCH] " lironh
2019-02-23 20:14 ` [dpdk-dev] [PATCH v2] " lironh
2019-02-25 11:29 ` Liron Himi
2019-03-10 14:27 ` Liron Himi
2019-03-13 16:57 ` Ferruh Yigit
2019-03-14 6:37 ` Liron Himi
2019-03-14 6:37 ` Liron Himi
2019-03-14 9:28 ` Ferruh Yigit
2019-03-14 9:28 ` Ferruh Yigit
2019-03-15 17:02 ` Liron Himi
2019-03-15 17:02 ` Liron Himi
2019-03-15 17:59 ` Ferruh Yigit
2019-03-15 17:59 ` Ferruh Yigit
2019-03-17 9:43 ` Liron Himi
2019-03-17 9:43 ` Liron Himi
2019-03-20 19:48 ` Ferruh Yigit
2019-03-20 19:48 ` Ferruh Yigit
2019-03-22 18:12 ` [dpdk-dev] [PATCH v3] " lironh
2019-03-22 18:12 ` lironh
2019-03-23 21:48 ` Rami Rosen
2019-03-23 21:48 ` Rami Rosen
2019-03-24 10:05 ` Liron Himi [this message]
2019-03-24 10:05 ` [dpdk-dev] [EXT] " Liron Himi
2019-03-24 12:15 ` [dpdk-dev] [PATCH v4] " lironh
2019-03-24 12:15 ` lironh
2019-03-25 15:44 ` Ferruh Yigit
2019-03-25 15:44 ` Ferruh Yigit
2019-03-25 20:48 ` [dpdk-dev] [PATCH v5] " lironh
2019-03-25 20:48 ` lironh
2019-03-25 21:11 ` Ferruh Yigit
2019-03-25 21:11 ` Ferruh Yigit
2019-03-26 18:40 ` [dpdk-dev] [PATCH v6] " lironh
2019-03-26 17:59 ` Ferruh Yigit
2019-03-26 17:59 ` Ferruh Yigit
2019-03-30 0:00 ` Thomas Monjalon
2019-03-30 0:00 ` Thomas Monjalon
2019-03-26 18:40 ` lironh
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=MN2PR18MB23981CEC3FD9991B0CD38041C65D0@MN2PR18MB2398.namprd18.prod.outlook.com \
--to=lironh@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ramirose@gmail.com \
--cc=walan@marvell.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).