ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: NTG ConTeXt Mailing List <ntg-context@ntg.nl>
Subject: Re: New context version...
Date: Tue, 06 Nov 2001 16:25:50 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20011106162225.037491f8@server-1> (raw)
In-Reply-To: <20011106155831.A1598@bart.math.muni.cz>

At 03:58 PM 11/6/2001 +0100, David Antos wrote:
>On Tue, Nov 06, 2001 at 03:05:24PM +0100, Taco Hoekwater wrote:
> >
> > Hi Hans,
> >
> > This is unrelated. I got curious and did some searching on the web.  The
> > kapm-idled is a kernel thread that executes the HLT instruction if the 
> kernel
> > has nothing better to do. Reason (sort of correct): the chip consumes less
> > power when executing HLT than when doing nothing ;)
>
>Hi, Taco was faster than me and absolutelly correct. The power saving is not
>the only reason, each Un*x has a process with the lowest possible priority
>which runs when there is nothing to do. Some kind of that behaviour occurs in
>all OSs. One possibility is to execute HLT, another is an infinite loop. 
>HLT is
>prefered as it saves energy and makes CPU cooler.

That's interesting! When I run linux undocked i'll do another test and see 
if there's a priority bug involved.

I just ran a couple of tests with docked linux and the maps test file runs 
in some 3 seconds less that windows, partly because mpost runs smoother 
from within tex under linux [i'm still hoping that fabrice will make this 
nice mpost dll that stays in mem]

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  parent reply	other threads:[~2001-11-06 15:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Your message of "Mon, 05 Nov 2001 15:17:46 +0100." <5.1.0.14.1.20011105151614.03e65e78@server-1>
2001-11-05 14:46 ` Patrick Gundlach
2001-11-05 15:55   ` Hans Hagen
2001-11-05 19:50     ` David Antos
2001-11-06  9:33       ` Hans Hagen
     [not found]         ` <20011106150524.2ac086b4.taco@elvenkind.com>
2001-11-06 14:58           ` David Antos
2001-11-06 14:50             ` Frans Goddijn
2001-11-06 15:25             ` Hans Hagen [this message]
2001-11-07  0:25         ` Berend de Boer
2001-11-05 15:26 ` Accents too high Patrick Gundlach
2001-11-05 16:27   ` Hans Hagen
2001-11-05 17:52     ` Patrick Gundlach
2001-11-06  9:39       ` Hans Hagen
2005-08-28 16:55 New context version Rob Ermers
2005-08-28 18:38 ` Taco Hoekwater
2005-08-28 21:43   ` Rob Ermers
2005-08-29 13:19     ` Hans Hagen
2005-08-29 13:22       ` r.ermers
  -- strict thread matches above, loose matches on Subject: below --
2005-08-28 14:04 Rob Ermers
     [not found] <Your message of "Mon, 05 Nov 2001 13:38:31 +0100." <5.1.0.14.1.20011105133734.0311b2f8@server-1>
2001-11-05 14:07 ` Accents too high Patrick Gundlach
2001-11-05 13:45   ` Frans Goddijn
2001-11-05 14:17   ` Hans Hagen

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=5.1.0.14.1.20011106162225.037491f8@server-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /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).