From: ralph@inputplus.co.uk (Ralph Corderoy)
Subject: [TUHS] Date madness
Date: Sat, 16 Dec 2017 17:11:32 +0000 [thread overview]
Message-ID: <20171216171132.4D5ED21CB8@orac.inputplus.co.uk> (raw)
In-Reply-To: <1513440719.1943285.1207178784.050ABA15@webmail.messagingengine.com>
Hi Randy,
> One way the kernel could tell old from new inodes is by reserving the
> high bit of one of the current 32-bit fields
When Doug mentioned the high bit being an escape I assumed something
like, using eight bits for ease,
00-7f existing positive meaning
80-df new meaning as if unsigned
e0-ff existing negative meaning
existing 80 81...df e0...fe ff 00 01...7f
new e0...fe ff 00 01...7f 80 81..df
This would extend the positive range beyond 2038, but keep a small range
of negatives for their existing pre-1970 meaning. This is storage
representation. Calculations can be done in a wider int, with
intermediate values simply being signed, as before.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
next prev parent reply other threads:[~2017-12-16 17:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 10:50 Doug McIlroy
2017-12-16 16:11 ` Random832
2017-12-16 17:11 ` Ralph Corderoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-13 22:16 Norman Wilson
2017-12-14 0:24 ` Chris Torek
2017-12-17 16:20 ` Ron Natalie
2017-12-17 18:53 ` Tom Ivar Helbekkmo
2017-12-17 20:07 ` Ron Natalie
2017-12-13 20:22 Noel Chiappa
2017-12-13 19:12 Doug McIlroy
2017-12-14 3:07 ` Random832
2017-12-15 3:04 ` Random832
2017-12-13 17:16 Noel Chiappa
2017-12-13 18:53 ` Tom Ivar Helbekkmo
2017-12-13 20:46 ` arnold
2017-12-15 16:41 ` Paul Winalski
2017-12-15 17:19 ` Dave Horsfall
2017-12-16 15:45 ` Clem Cole
2017-12-16 3:39 ` Dave Horsfall
2017-12-16 3:45 ` Lyndon Nerenberg
2017-12-17 1:43 ` Dave Horsfall
2017-12-14 3:08 ` Dave Horsfall
2017-12-14 3:13 ` Warner Losh
2017-12-13 16:31 Noel Chiappa
2017-12-13 16:50 ` arnold
2017-12-13 16:08 Noel Chiappa
2017-12-13 16:23 ` arnold
2017-12-13 15:56 Noel Chiappa
2017-12-12 18:31 Noel Chiappa
2017-12-12 18:01 Noel Chiappa
2017-12-12 18:21 ` Warner Losh
2017-12-13 15:07 ` Random832
2017-12-13 17:00 ` Jason Stevens
2017-12-13 17:18 ` Ron Natalie
2017-12-13 18:02 ` Arthur Krewat
2017-12-13 15:39 ` Wolfgang Helbig
2017-12-14 0:57 ` Dave Horsfall
2017-12-14 14:09 ` William Cheswick
2017-12-17 16:19 ` Ron Natalie
2017-12-17 16:33 ` William Cheswick
2017-12-17 17:54 ` Random832
2017-12-17 22:15 ` Dave Horsfall
2017-12-17 22:54 ` Ian Zimmerman
2017-12-16 18:12 ` Wolfgang Helbig
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=20171216171132.4D5ED21CB8@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
/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).