[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc219fe5f8c8dec66a6fdff08f40acf714b8328b.camel@amazon.com>
Date: Wed, 9 Aug 2023 13:53:26 +0000
From: "Erdogan, Tahsin" <trdgn@...zon.com>
To: "herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"willemdebruijn.kernel@...il.com" <willemdebruijn.kernel@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"pabeni@...hat.com" <pabeni@...hat.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] tun: avoid high-order page allocation for packet header
On Wed, 2023-08-09 at 09:18 -0400, Willem de Bruijn wrote:
> Tun sendmsg is a special case, only used by vhost-net from inside the
> kernel. Arguably consistency with packet_snd/packet_alloc_skb would
> be
> more important. That said, this makes sense to me. I assume your
> configuring a device with very large MTU?
That's right. I am setting MTU to 9100 in my test.
Powered by blists - more mailing lists