From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH 0/2] udevd: Optimize "goto"
Date: Sun, 28 Sep 2008 11:00:29 +0000 [thread overview]
Message-ID: <48DF63CD.6070507@tuffmail.co.uk> (raw)
I seem to remember you mentioned this as a longer-term goal. This was
in the context of the TODO item "rework rules to a match-action list,
instead of a rules array".
The idea was to move the scan for the label targeted by a goto rule
(udev_rules_iter_label), from run-time to parse-time. It avoids
repeating the scan for every event.
I already had a patch for this specific idea. I think it can be
implemented now without causing problems. It's no big win - cachegrind
suggests it takes 5% off user cpu time - but it is progress.
reply other threads:[~2008-09-28 11:00 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=48DF63CD.6070507@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.