9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Dorman eld@jewel.ucsd.edu
Subject: [9fans] DPT PM2041W observations
Date: Mon, 12 Jan 1998 15:17:31 -0800	[thread overview]
Message-ID: <19980112231731._J8tDk-XxNuBDmr7DPj1-EFggZqBKWcdfldRxKWNfII@z> (raw)


Gdb wrote:
> Date: Mon, 12 Jan 1998 14:52:37 -0600
> From: "G. David Butler" <gdb@dbSystems.com>
 
> >> So why does this 4th generation card with tag queueing support
> >> run slower than the 1st generation design that is over 10 years
> >> old?
> >Perhaps the driver for the 1540 is better optimized as it's been
> >around longer, and it's had more work put into it.  There might
> Remember, I have written both drivers from scratch and each
> is optimized for the controller it is talking to.

  Is it?  I gathered from your original post that your guide was 
the BSDi DPT driver, and teaching the 154x driver to talk to the 
DPT; the DPT docs weren't mentioned..  Is the BSDi driver considered 
definative?

  Historically I vaguely recall the DPT ppl claiming their card 
was 'faster' than a 154x, but that may be only for certain subsets 
of problems.  DPT may be interested in discovering why, for this 
test, it apparently loses out.. then again, as PCI has supplanted 
ISA for this application, maybe not.  

  Do you have a caching module?  It may be that w/o one the card 
isin't a win.  The caching might also take advantage of a request
distribution similar to the usual Micro$sloth stuff which isin't
valid for Plan9.
 
> David Butler
> gdb@dbSystems.com

Regards,

Eric Dorman
edorman@ucsd.edu





             reply	other threads:[~1998-01-12 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-12 23:17 Eric [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-01-14 22:56 Mark
1998-01-14 14:57 G.David
1998-01-12 23:18 G.David
1998-01-12 20:52 G.David
1998-01-12 20:38 Eric
1998-01-12 19:58 G.David
1998-01-12  0:19 G.David

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=19980112231731._J8tDk-XxNuBDmr7DPj1-EFggZqBKWcdfldRxKWNfII@z \
    --to=9fans@9fans.net \
    /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).