From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 206919] New: Very bad performance of sendto function
Date: Mon, 23 Mar 2020 09:59:18 -0700 [thread overview]
Message-ID: <20200323095918.1f6d6400@hermes.lan> (raw)
There maybe something here but probably not.
Begin forwarded message:
Date: Sun, 22 Mar 2020 11:22:46 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 206919] New: Very bad performance of sendto function
https://bugzilla.kernel.org/show_bug.cgi?id=206919
Bug ID: 206919
Summary: Very bad performance of sendto function
Product: Networking
Version: 2.5
Kernel Version: 5.4.13
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: bernat.arlandis@gmail.com
Regression: No
Created attachment 288007
--> https://bugzilla.kernel.org/attachment.cgi?id=288007&action=edit
Sysprof capture file
Hi,
I have a case where the sendto function is slowing down the software I'm trying
to use. Sysprof capture file attached.
It's probably being called at a high frequency and the __netlink_dump_start
function spends a lot of time in the mutex lock, then also in the netlink_dump
call.
This is causing the threads calling the function to stall. At least this is my
interpretation of the profiling session.
I don't have any knowledge about the way networking code works. I'd like to
know if the flaw is in the user-space software or in the kernel. Can I provide
any more info or do some test to help determine what's happening? I'd like to
help fix it.
My NIC: Intel Corporation I211 Gigabit Network Connection (rev 03)
My system: Debian 10 with kernel 5.4.13.
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-03-23 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 16:59 Stephen Hemminger [this message]
2020-03-25 17:13 ` [Bug 206919] New: Very bad performance of sendto function David Laight
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=20200323095918.1f6d6400@hermes.lan \
--to=stephen@networkplumber.org \
--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).