From: Paolo Abeni <pabeni@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>, netdev@vger.kernel.org
Cc: vladbu@mellanox.com, pablo@netfilter.org,
xiyou.wangcong@gmail.com, jhs@mojatatu.com, mlxsw@mellanox.com,
alexanderk@mellanox.com
Subject: Re: tc tp creation performance degratation since kernel 5.1
Date: Wed, 12 Jun 2019 14:30:37 +0200 [thread overview]
Message-ID: <e11118334595e6517e618e80406e0135402cacf1.camel@redhat.com> (raw)
In-Reply-To: <20190612120341.GA2207@nanopsycho>
Hi,
On Wed, 2019-06-12 at 14:03 +0200, Jiri Pirko wrote:
> I did simple prifiling using perf. Output on 5.1 kernel:
> 77.85% tc [kernel.kallsyms] [k] tcf_chain_tp_find
> 3.30% tc [kernel.kallsyms] [k] _raw_spin_unlock_irqrestore
> 1.33% tc_pref_scale.s [kernel.kallsyms] [k] do_syscall_64
> 0.60% tc_pref_scale.s libc-2.28.so [.] malloc
> 0.55% tc [kernel.kallsyms] [k] mutex_spin_on_owner
> 0.51% tc libc-2.28.so [.] __memset_sse2_unaligned_erms
> 0.40% tc_pref_scale.s libc-2.28.so [.] __gconv_transform_utf8_internal
> 0.38% tc_pref_scale.s libc-2.28.so [.] _int_free
> 0.37% tc_pref_scale.s libc-2.28.so [.] __GI___strlen_sse2
> 0.37% tc [kernel.kallsyms] [k] idr_get_free
>
> Output on net-next:
> 39.26% tc [kernel.vmlinux] [k] lock_is_held_type
It looks like you have lockdep enabled here, but not on the 5.1 build.
That would explain such a large perf difference.
Can you please double check?
thanks,
Paolo
next prev parent reply other threads:[~2019-06-12 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 12:03 tc tp creation performance degratation since kernel 5.1 Jiri Pirko
2019-06-12 12:30 ` Paolo Abeni [this message]
2019-06-13 4:50 ` Jiri Pirko
2019-06-12 12:34 ` Vlad Buslov
2019-06-13 5:49 ` Jiri Pirko
2019-06-13 8:11 ` Jiri Pirko
2019-06-13 10:09 ` Vlad Buslov
2019-06-13 11:11 ` Jiri Pirko
2019-06-13 11:26 ` Vlad Buslov
2019-06-13 14:18 ` Jiri Pirko
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=e11118334595e6517e618e80406e0135402cacf1.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=alexanderk@mellanox.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vladbu@mellanox.com \
--cc=xiyou.wangcong@gmail.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).