From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] Invalidating udev cache...
Date: Tue, 14 Apr 2009 19:46:09 -0400 [thread overview]
Message-ID: <20090414234609.GA27890@denix.org> (raw)
On Tue, Mar 03, 2009 at 08:16:48AM -0700, Tom Rini wrote:
> On Tue, Mar 03, 2009 at 08:24:44AM +0100, Koen Kooi wrote:
> > On 03-03-09 06:11, Denys Dmytriyenko wrote:
> >> On Thu, Dec 04, 2008 at 06:41:50PM +0100, Koen Kooi wrote:
> >>> On 04-12-08 18:09, Mike (mwester) wrote:
> >>>> Mike (mwester) wrote:
> >>>>
> >>>>> A slight improvement would be to make the dev.tar file dependent upon
> >>>>> the bootargs; i.e. invalidate /etc/dev.tar file if the boot command line
> >>>>> doesn't match the current command line. This could be a very fast
> >>>>> operation, just "cmp /proc/cmdline /etc/dev_cmdline" or similar.
> >>>> As I consider this further, we could actually just save and compare
> >>>> /proc/atags if that's present on the device in question (falling back to
> >>>> /proc/cmdline if not present). That would catch *any* changes passed in
> >>>> to the kernel via the bootloader.
> >>>>
> >>>> Flashing a new kernel would seem to be another logical place to
> >>>> invalidate the cache, so adding a comparison of "uname -rv" would be a
> >>>> reasonable way to catch that.
> >>> That should indeed take care of bootargs and kernel version changes. I'm
> >>> still tempted to add option 2) to all that :)
> >>
> >> Sorry for bringing up this old discussion. Are there any plans to implement
> >> the above checks in udev?
> >
> > Plans yes, time no :(
>
> Can we make sure they're optional?
I'd like to revive this old topic and propose a patch, which implements most
of the above points. I'm not sure about making it optional and /proc/atags.
So, anyway, the patch will follow, please provide comments.
--
Denys
next reply other threads:[~2009-04-14 23:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 23:46 Denys Dmytriyenko [this message]
2009-04-14 23:49 ` [PATCH] udev 124: add cache invalidation logic on kernel change or its bootargs/cmdline Denys Dmytriyenko
2009-04-15 6:47 ` Koen Kooi
2009-04-15 6:54 ` Holger Schurig
2009-04-16 0:06 ` Denys Dmytriyenko
2009-04-16 12:34 ` Otavio Salvador
2009-04-16 13:04 ` Koen Kooi
2009-04-16 16:33 ` Tom Rini
2009-04-18 9:31 ` Koen Kooi
2009-04-18 17:56 ` Tom Rini
2009-04-18 18:56 ` Mike (mwester)
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=20090414234609.GA27890@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.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