From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: nfsrahead possible optimization for udev rule
Date: Thu, 16 May 2024 23:07:20 +0200 [thread overview]
Message-ID: <28702298-1c16-427f-b7df-3fbca3f78e9b@gmail.com> (raw)
Hi
I'm looking at some performance graphs and udev rule 99-nfs.rules seems to be
taking some unnecessary CPU time when the system is creating and removing a
lot of devices in the system. It looks like 'nfsrahead' is always
'parsing' something in mnt_table_parse_line - while technically all
the entries in nfs.conf are simply commented out, so there is nothing
'nfsrahead' should be doing and it should just quickly exit.
Also is it really worth this done through udev system ? - when possibly thing
could be solved via udev monitoring in case something really is needed to
change these setting for BDI (although this change is substantially harder to
develop).
Regards
Zdenek
reply other threads:[~2024-05-16 21:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=28702298-1c16-427f-b7df-3fbca3f78e9b@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-nfs@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 read-only IMAP folder(s) and NNTP newsgroup(s).