From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: viro@zeniv.linux.org.uk, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, bugs@lists.linux.dev
Subject: large pause when opening file descriptor which is power of 2
Date: Wed, 26 Apr 2023 17:58:06 +0000 (UTC) [thread overview]
Message-ID: <20230426-b217366c0-53b6841a1f9a@bugzilla.kernel.org> (raw)
phemmer+kernel added an attachment on Kernel.org Bugzilla:
Created attachment 304186
issue demonstration code
When running a threaded program, and opening a file descriptor that is a power of 2 (starting at 64), the call takes a very long time to complete. Normally such a call takes less than 2us. However with this issue, I've seen the call take up to around 50ms. Additionally this only happens the first time, and not subsequent times that file descriptor is used. I'm guessing there might be some expansion of some internal data structures going on. But I cannot see why this process would take so long.
Attached is a simple program that can reproduce the issue. The following is example output:
...
FD=62 duration=2695
FD=63 duration=2726
FD=64 duration=12565293
FD=64 duration=3837 (second attempt)
FD=65 duration=1523
FD=66 duration=1533
...
FD=126 duration=1463
FD=127 duration=1402
FD=128 duration=24755063
FD=128 duration=3186 (second attempt)
FD=129 duration=1433
FD=130 duration=1413
...
FD=254 duration=1363
FD=255 duration=1493
FD=256 duration=7602777
FD=256 duration=1573 (second attempt)
FD=257 duration=1392
FD=258 duration=1363
...
I've reproduced the issue on systems running multiple different 4.19 kernels, and on a system running 6.2.8
File: fd_pause.c (text/x-csrc)
Size: 970.00 B
Link: https://bugzilla.kernel.org/attachment.cgi?id=304186
---
issue demonstration code
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next reply other threads:[~2023-04-26 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 17:58 Kernel.org Bugbot [this message]
2023-04-26 19:13 ` large pause when opening file descriptor which is power of 2 Matthew Wilcox
2023-04-26 19:46 ` Al Viro
2023-04-26 19:56 ` Matthew Wilcox
2023-04-26 20:33 ` Al Viro
2023-04-26 19:58 ` Al Viro
2023-04-26 23:42 ` Kernel.org Bugbot
2023-04-27 9:28 ` Christian Brauner
2023-04-27 18:18 ` Matthew Wilcox
2023-04-28 0:37 ` Kernel.org Bugbot
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=20230426-b217366c0-53b6841a1f9a@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=brauner@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).