Date: Mon, 11 Jun 2001 19:55:31 -0400
Message-Id: <200106112355.TAA12944@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <3c03g9.v17.ln@nix-if1> (yurick@oblik.dp.ua)
Subject: Re: __djgpp_map_physical_memory - some questions
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010606090422 DOT 14278F AT is> <3c03g9 DOT v17 DOT ln AT nix-if1>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Is DOS _really_ so slow?

No, but consider that Unix keeps track of the time *as* a time_t, so
time() merely reads a number from memory and returns it - a few CPU
cycles at best.  DOS, however, uses the hardware realtime clock, so it
must convert month/day/year/hour/minute/second/timezone to a time_t
each time you need to know what time it is.  The conversion is slow.