All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@innominate.de>
To: Joe deBlaquiere <jadb@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: more on scheduler benchmarks
Date: Wed, 24 Jan 2001 13:29:14 +0100	[thread overview]
Message-ID: <3A6ECA9A.AD9200E7@innominate.de> (raw)
In-Reply-To: <20010122101738.B7427@w-mikek.des.sequent.com> <3A6CEB02.3050906@redhat.com>

Joe deBlaquiere wrote:
> 
> Maybe I've been off in the hardware lab for too long, but how about
> 
> 1. using ioperm to give access to the parallel port.
> 2. have your program write a byte (thread id % 256 ?) constantly to the
> port during it's other activity
> 3. capture the results from another computer with an ecp port
> 
> This way you don't run the risk of altering the scheduler behavior with
> your logging procedure.

It's a technique I've used in debugging realtime systems.  It works
great, but bear in mind that the out to the parallel port costs an awful
lot of cycles.  You *will* alter the behaviour of\x13 the scheduler.

--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-24 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22 18:17 more on scheduler benchmarks Mike Kravetz
2001-01-22 18:37 ` Davide Libenzi
2001-01-23  2:22 ` Joe deBlaquiere
2001-01-24 12:29   ` Daniel Phillips [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-22 20:07 [Lse-tech] " Bill Hartner
2001-01-23 12:45 ` Andrew Morton

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=3A6ECA9A.AD9200E7@innominate.de \
    --to=phillips@innominate.de \
    --cc=jadb@redhat.com \
    --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.