From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Tahsin Erdogan <trdgn@amazon.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jason Wang <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Tahsin Erdogan <trdgn@amazon.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [PATCH v3] tun: avoid high-order page allocation for packet header
Date: Wed, 09 Aug 2023 09:18:22 -0400 [thread overview]
Message-ID: <64d3921ed1f1a_267bde294f2@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20230808230920.1944738-1-trdgn@amazon.com>
Tahsin Erdogan wrote:
> When GSO is not enabled
Not GSO, but gso.hdr_len, which is a feature of IFF_VNET_HDR.
VIRTIO_NET_HDR_GSO_* does not need to be enabled to use the
header length field.
> and a packet is transmitted via writev(), all
> payload is treated as header which requires a contiguous memory allocation.
> This allocation request is harder to satisfy, and may even fail if there is
> enough fragmentation.
>
> Note that sendmsg() code path limits the linear copy length, so this change
> makes writev() and sendmsg() more consistent.
This is not specific to writev(), equally to more common write().
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?
> Signed-off-by: Tahsin Erdogan <trdgn@amazon.com>
> ---
> v3: rebase to latest net-next
> v2: replace linear == 0 with !linear
> v1: https://lore.kernel.org/all/20230726030936.1587269-1-trdgn@amazon.com/
> drivers/net/tun.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index 5beb6b5dd7e5..53d19c958a20 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -1523,7 +1523,7 @@ static struct sk_buff *tun_alloc_skb(struct tun_file *tfile,
> int err;
>
> /* Under a page? Don't bother with paged skb. */
> - if (prepad + len < PAGE_SIZE || !linear)
> + if (prepad + len < PAGE_SIZE)
> linear = len;
>
> if (len - linear > MAX_SKB_FRAGS * (PAGE_SIZE << PAGE_ALLOC_COSTLY_ORDER))
> @@ -1913,6 +1913,9 @@ static ssize_t tun_get_user(struct tun_struct *tun, struct tun_file *tfile,
> */
> zerocopy = false;
> } else {
> + if (!linear)
> + linear = min_t(size_t, good_linear, copylen);
> +
> skb = tun_alloc_skb(tfile, align, copylen, linear,
> noblock);
> }
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-08-09 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 23:09 [PATCH v3] tun: avoid high-order page allocation for packet header Tahsin Erdogan
2023-08-09 13:18 ` Willem de Bruijn [this message]
2023-08-09 13:53 ` Erdogan, Tahsin
2023-08-09 14:01 ` Willem de Bruijn
2023-08-09 15:01 ` Erdogan, Tahsin
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=64d3921ed1f1a_267bde294f2@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=trdgn@amazon.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).