From: David Miller <davem@davemloft.net>
To: ilant@mellanox.com
Cc: netdev@vger.kernel.org, alexander.h.duyck@intel.com,
eric.dumazet@gmail.com, steffen.klassert@secunet.com,
borisp@mellanox.com
Subject: Re: [PATCH net-next] gso: Support frag_list splitting with head_frag
Date: Wed, 12 Apr 2017 13:54:02 -0400 (EDT) [thread overview]
Message-ID: <20170412.135402.144775618564874368.davem@davemloft.net> (raw)
In-Reply-To: <20170407230708.18967-1-ilant@mellanox.com>
From: <ilant@mellanox.com>
Date: Sat, 8 Apr 2017 02:07:08 +0300
> From: Ilan Tayari <ilant@mellanox.com>
>
> A driver may use build_skb() for received packets.
> These SKBs then have a head_frag.
>
> Since commit d7e8883cfcf4 ("net: make GRO aware of
> skb->head_frag"), GRO may build frag_list SKBs out of
> head_frag received SKBs.
> In such a case, the chained SKBs end up with a head_frag.
>
> Commit 07b26c9454a2 ("gso: Support partial splitting at
> the frag_list pointer") adds partial segmentation of frag_list
> SKB chains into individual SKBs.
> However, this is not done if the chained SKBs have any
> linear part, because the device may not be able to DMA
> the private linear buffer.
>
> A chained frag_list SKB with head_frag is wrongfully
> detected in this case as having a private linear part
> and thus falls back to software GSO, while in fact the
> linear part is backed by a DMA page just like any other frag.
>
> This causes low performance when forwarding those packets
> that were built with build_skb()
>
> Allow partial segmentation at the frag_list pointer for
> chained SKBs with head_frag.
>
> Note that such SKBs can only be created by GRO, when applied
> to received packets with head_frag.
> Also note that this change only affects the data path that
> performs the partial segmentation at frag_list pointer, and
> not any of the other more common data paths.
>
> Signed-off-by: Ilan Tayari <ilant@mellanox.com>
Applied, thank you for the detailed commit message.
prev parent reply other threads:[~2017-04-12 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 23:07 [PATCH net-next] gso: Support frag_list splitting with head_frag ilant
2017-04-12 17:54 ` David Miller [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=20170412.135402.144775618564874368.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=borisp@mellanox.com \
--cc=eric.dumazet@gmail.com \
--cc=ilant@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).