From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219141] nfs slow , rw error ffast write
Date: Thu, 08 Aug 2024 13:47:54 +0000 [thread overview]
Message-ID: <bug-219141-13602-ONpjulKq4y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219141-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219141
Christian Kujau (kernel@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kernel@nerdbynature.de
--- Comment #1 from Christian Kujau (kernel@nerdbynature.de) ---
Analyzing performance issues can be tricky, or even impossible with so little
information to go by. Since you seem to test RC kernels, maybe try to bisect
the deadlocks and slow reads via Git bisect:
https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html to help
debugging this one.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2024-08-08 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 11:41 [Bug 219141] New: nfs slow , rw error ffast write bugzilla-daemon
2024-08-08 13:47 ` bugzilla-daemon [this message]
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=bug-219141-13602-ONpjulKq4y@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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