From: Paolo Abeni <pabeni@redhat.com>
To: Jason Wang <jasowang@redhat.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next] net: core: rework skb_probe_transport_header()
Date: Thu, 03 May 2018 19:22:11 +0200 [thread overview]
Message-ID: <1525368131.3233.5.camel@redhat.com> (raw)
In-Reply-To: <87edeb52-c159-2f72-1daa-75731f0c9d42@redhat.com>
On Thu, 2018-05-03 at 20:55 +0800, Jason Wang wrote:
>
> On 2018年05月03日 17:35, Paolo Abeni wrote:
> > When the transport header is not available, skb_probe_transport_header()
> > resorts to fully dissect the flow keys, even if it only needs the
> > ransport offset. We can obtain the latter using a simpler flow dissector -
> > flow_keys_buf_dissector - and a smaller struct for key storage.
> >
> > The above gives ~50% performance improvement in micro benchmarking around
> > skb_probe_transport_header(), mostly due to the smaller memset. Small, but
> > measurable improvement is measured also in macro benchmarking - raw xmit
> > tput from a VM.
> >
> > Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> > ---
> > include/linux/skbuff.h | 7 +++++--
> > include/net/flow_dissector.h | 5 +++++
> > net/core/flow_dissector.c | 1 +
> > 3 files changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> > index 908d66e55b14..63cb523d3519 100644
> > --- a/include/linux/skbuff.h
> > +++ b/include/linux/skbuff.h
> > @@ -2350,11 +2350,14 @@ static inline void skb_pop_mac_header(struct sk_buff *skb)
> > static inline void skb_probe_transport_header(struct sk_buff *skb,
> > const int offset_hint)
> > {
> > - struct flow_keys keys;
> > + struct flow_keys_basic keys;
> >
> > if (skb_transport_header_was_set(skb))
> > return;
> > - else if (skb_flow_dissect_flow_keys(skb, &keys, 0))
> > +
> > + memset(&keys, 0, sizeof(keys));
> > + if (__skb_flow_dissect(skb, &flow_keys_buf_dissector, &keys,
> > + 0, 0, 0, 0, 0))
> > skb_set_transport_header(skb, keys.control.thoff);
> > else
> > skb_set_transport_header(skb, offset_hint);
> > diff --git a/include/net/flow_dissector.h b/include/net/flow_dissector.h
> > index 9a074776f70b..e81dab6e9ac6 100644
> > --- a/include/net/flow_dissector.h
> > +++ b/include/net/flow_dissector.h
> > @@ -226,6 +226,11 @@ struct flow_dissector {
> > unsigned short int offset[FLOW_DISSECTOR_KEY_MAX];
> > };
> >
> > +struct flow_keys_basic {
> > + struct flow_dissector_key_control control;
> > + struct flow_dissector_key_basic basic;
> > +};
> > +
> > struct flow_keys {
> > struct flow_dissector_key_control control;
> > #define FLOW_KEYS_HASH_START_FIELD basic
> > diff --git a/net/core/flow_dissector.c b/net/core/flow_dissector.c
> > index d29f09bc5ff9..ac7b4de4a0f0 100644
> > --- a/net/core/flow_dissector.c
> > +++ b/net/core/flow_dissector.c
> > @@ -1418,6 +1418,7 @@ struct flow_dissector flow_keys_dissector __read_mostly;
> > EXPORT_SYMBOL(flow_keys_dissector);
> >
> > struct flow_dissector flow_keys_buf_dissector __read_mostly;
> > +EXPORT_SYMBOL(flow_keys_buf_dissector);
> >
> > static int __init init_default_flow_dissectors(void)
> > {
>
> Acked-by: Jason Wang <jasowang@redhat.com>
>
> Just curious, I believe this happens only when csum offload is disabled
> which is not the common case?
This also happens if the VM is doing L2 forwarding (and L3 I think)
with offload enabled.
Cheers,
Paolo
next prev parent reply other threads:[~2018-05-03 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 9:35 [PATCH net-next] net: core: rework skb_probe_transport_header() Paolo Abeni
2018-05-03 12:55 ` Jason Wang
2018-05-03 17:22 ` Paolo Abeni [this message]
2018-05-03 17:32 ` David Miller
2018-05-03 17:59 ` Paolo Abeni
2018-05-03 18:22 ` David Miller
2018-05-04 21:35 ` kbuild test robot
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=1525368131.3233.5.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=netdev@vger.kernel.org \
/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).