From: Eric Dumazet <eric.dumazet@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [RFC PATCH] net/sched: add indirect call wrapper hint.
Date: Thu, 18 Jun 2020 12:00:13 -0700 [thread overview]
Message-ID: <0240746c-1dd1-4822-261c-03ff13854db2@gmail.com> (raw)
In-Reply-To: <da175b76ca89e57876cf55d3d56aef126054d12c.1592501362.git.pabeni@redhat.com>
On 6/18/20 10:31 AM, Paolo Abeni wrote:
> The sched layer can use several indirect calls per
> packet, with not work-conservative qdisc being
> more affected due to the lack of the BYPASS path.
>
> This change tries to improve the situation using
> the indirect call wrappers infrastructure for the
> qdisc enqueue end dequeue indirect calls.
>
> To cope with non-trivial scenarios, a compile-time know is
> introduced, so that the qdisc used by ICW can be different
> from the default one.
>
> Tested with pktgen over qdisc, with CONFIG_HINT_FQ_CODEL=y:
>
> qdisc threads vanilla patched delta
> nr Kpps Kpps %
> pfifo_fast 1 3300 3700 12
> pfifo_fast 2 3940 4070 3
> fq_codel 1 3840 4110 7
> fq_codel 2 1920 2260 17
> fq 1 2230 2210 -1
> fq 2 1530 1540 1
Hi Paolo
This test is a bit misleading, pktgen has a way to bypass the qdisc.
Real numbers for more typical workloads would be more appealing,
before we consider a quite invasive patch ?
What is the status of static_call infrastructure ?
>
> +#ifndef CODEL_SCOPE
> +#define CODEL_SCOPE static
> +#endif
This looks additional burden, just remove the static attribute,
if a function might be called directly.
Eg, we have EXPORT_SYMBOL() all over the places, even if the modules needing
a symbol might not be compiled at all, or being part of vmlinux.
Thanks !
next prev parent reply other threads:[~2020-06-18 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 17:31 [RFC PATCH] net/sched: add indirect call wrapper hint Paolo Abeni
2020-06-18 19:00 ` Eric Dumazet [this message]
2020-06-19 9:24 ` Paolo Abeni
2020-06-22 9:38 ` Paolo Abeni
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=0240746c-1dd1-4822-261c-03ff13854db2@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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