public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Ben Elliston <bje@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: modeling latency (fwd)
Date: Thu, 21 Jun 2001 04:21:00 -0000	[thread overview]
Message-ID: <20010621072133.A4390@redhat.com> (raw)
In-Reply-To: <15153.37541.916886.137745@scooby.brisbane.redhat.com>

Hi -

bje wrote:
: [...]
:   FChE> (ditto, to account for cache hit times & miss penalties), all the way
:   FChE> to the CPU.  (The "sid::bus::delayed" indication can finally die.)
: 
: What was the intention of the delayed indication?  [...]

It was to be a different way of representing bus latency.  Instead of
merely counting cycles, the bus::delayed indication was to tell the
bus master to yield to the target scheduler for a while, and try
again later.  There is some theoretical appeal, but implementing it
this way is too complicated.  For example, it would require making
all CPU memory access calls points abort/restartable; it would involve
the target scheduler a lot.  I believe some sid alumni had the same
ideas, but never got around to expressing them (and obviously to
implementing them).

IMO it can go away altogether.

BTW, regarding the proposed bus::status patch, it would be nice if you
could find some way of ensuring/requesting that the compiler packs the
struct into 4 bytes.  Maybe the g++ "enum foo : 16" extension, maybe
something else.

- FChE
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7Mdi9VZbdDOm/ZT0RAkUIAJ9U+zgxa7u/FcThN6Hs9vcvRRZrDgCdEJ1K
9ehrlze9/q6ml8Xk28FbpKo=
=bUh0
-----END PGP SIGNATURE-----

  reply	other threads:[~2001-06-21  4:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17 20:28 Ben Elliston
2001-06-20 23:23 ` Ben Elliston
2001-06-21  4:21   ` Frank Ch. Eigler [this message]
2001-06-24 17:06     ` Ben Elliston
2001-06-24 17:46       ` Frank Ch. Eigler
2001-06-24 18:52         ` Ben Elliston

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=20010621072133.A4390@redhat.com \
    --to=fche@redhat.com \
    --cc=bje@redhat.com \
    --cc=sid@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).