All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: lironh@marvell.com
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>, walan@marvell.com
Subject: Re: [PATCH v6] net/kni: calc mbuf&mtu according to given mb_pool
Date: Sat, 30 Mar 2019 01:00:22 +0100	[thread overview]
Message-ID: <1583987.qdoNeV79LG@xps> (raw)
In-Reply-To: <8fbf0397-42b1-ba11-d7eb-34bf0b404355@intel.com>

26/03/2019 18:59, Ferruh Yigit:
> On 3/26/2019 6:40 PM, lironh@marvell.com wrote:
> > From: Liron Himi <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>
> 
> Suggested title:
> kni: calculate MTU from mbuf buffer size
> 
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied, thanks

      reply	other threads:[~2019-03-30  0:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21  8:47 [PATCH] net/kni: calc mbuf&mtu according to given mb_pool lironh
2019-02-23 20:14 ` [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  9:28           ` Ferruh Yigit
2019-03-15 17:02             ` Liron Himi
2019-03-15 17:59               ` Ferruh Yigit
2019-03-17  9:43                 ` Liron Himi
2019-03-20 19:48                   ` Ferruh Yigit
2019-03-22 18:12   ` [PATCH v3] " lironh
2019-03-23 21:48     ` Rami Rosen
2019-03-24 10:05       ` [EXT] " Liron Himi
2019-03-24 12:15     ` [PATCH v4] " lironh
2019-03-25 15:44       ` Ferruh Yigit
2019-03-25 20:48       ` [PATCH v5] " lironh
2019-03-25 21:11         ` Ferruh Yigit
2019-03-26 18:40         ` [PATCH v6] " lironh
2019-03-26 17:59           ` Ferruh Yigit
2019-03-30  0:00             ` Thomas Monjalon [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=1583987.qdoNeV79LG@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=lironh@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.