From: "David S. Miller" <davem@redhat.com>
To: alan@lxorguk.ukuu.org.uk
Cc: bunk@fs.tum.de, jochen@scram.de, linux-kernel@vger.kernel.org
Subject: Re: 2.3.39 compile errors on Alpha
Date: Mon, 30 Sep 2002 13:39:04 -0700 (PDT) [thread overview]
Message-ID: <20020930.133904.96601483.davem@redhat.com> (raw)
In-Reply-To: <1033391751.16468.51.camel@irongate.swansea.linux.org.uk>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: 30 Sep 2002 14:15:50 +0100
Because I was looking over the gettimeoffset code and forgot that
gettimeofday itself takes the xtime_lock 8)
It used to be possible to implement this lockless using a $(sizeof
xtime)-bit load. But once you start adding complications such as
wall_jiffies, it isn't feasible anymore.
The next idea is to have a tick cookie that could later be converted
to/from a full timeval. This trick doesn't work on things like Alpha
where the guarenteed life of the tick is only 6 seconds or something
like that.
Most of the time the timestamp isn't even used.
If someone can propose other ideas I'm ready and listening :-)
next prev parent reply other threads:[~2002-09-30 20:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 7:46 2.3.39 compile errors on Alpha Jochen Friedrich
2002-09-30 7:59 ` Jochen Friedrich
2002-09-30 11:08 ` Adrian Bunk
2002-09-30 12:35 ` Alan Cox
2002-09-30 12:25 ` David S. Miller
2002-09-30 13:15 ` Alan Cox
2002-09-30 13:20 ` 2.5.39 XConfig Processor Detection Adam Voigt
2002-09-30 13:30 ` Dave Jones
2002-09-30 13:48 ` Adam Voigt
2002-09-30 20:39 ` David S. Miller [this message]
2002-09-30 17:58 ` 2.3.39 LLC on Alpha broken? Jochen Friedrich
2002-09-30 18:07 ` Arnaldo Carvalho de Melo
2002-09-30 8:04 ` Jochen Friedrich
2002-09-30 21:04 ` Jochen Friedrich
2002-10-01 14:46 ` Ivan Kokshaysky
2002-10-01 16:05 ` Falk Hueffner
2002-09-30 20:59 ` David S. Miller
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=20020930.133904.96601483.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@fs.tum.de \
--cc=jochen@scram.de \
--cc=linux-kernel@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.