From: Chris Friesen <chris_friesen@sympatico.ca>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH[ udevd race conditions and performance, assorted cleanups
Date: Mon, 29 Mar 2004 04:47:22 +0000 [thread overview]
Message-ID: <4067AA5A.7070707@sympatico.ca> (raw)
In-Reply-To: <4065078F.1070008@sympatico.ca>
Kay Sievers wrote:
> Chris,
> here is a patch on top of your nice improvements.
> I fixed the whitespace and it hopefully fixes the stupid timestamp bug in
> udevd. Some stupid OS sets the hwclock to localtime and linux changes it
> to UTC while starting. If any events are pending they may be delayed by
> the users time distance from UTC :) So we use the uptime seconds now.
Looks good. Sorry about the whitespace stuff...I forgot to change my
settings back after working on another project.
About the time stuff. Wouldn't it be nice if glibc had a wrapper around
the various ways to get a high resolution monotonically increasing
64-bit timestamp of "time since boot"? So for x86 you'd end up using
the tsc, for ppc you'd use the tbr, etc, etc. Currently we've got no
portable way to get a high res time that can't go backwards.
Chris
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-03-29 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 4:48 [PATCH[ udevd race conditions and performance, assorted cleanups Chris Friesen
2004-03-27 11:30 ` Kay Sievers
2004-03-28 1:08 ` Kay Sievers
2004-03-29 4:47 ` Chris Friesen [this message]
2004-03-31 23:04 ` Greg KH
2004-03-31 23:04 ` Greg KH
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=4067AA5A.7070707@sympatico.ca \
--to=chris_friesen@sympatico.ca \
--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 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).