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 12:38:56 -0800	[thread overview]
Message-ID: <19980112203856.YMmLmyUHBJfpTZ9BZ6YLzbbYaSgux8XvR34b2iOsp4A@z> (raw)


> Date: Mon, 12 Jan 1998 13:58:43 -0600
> From: "G. David Butler" <gdb@dbSystems.com>
> To: 9fans@cse.psu.edu
> Subject: Re: [9fans] DPT PM2041W observations
> 
> >If the answer to that is "yes, with Tag Queueing", then I
> >need some kind soul to help me get that to happen on the
> >DPT adapter.  (The 154x can't do that.)  None of the
> >documentation or source I have enable that feature.
> 
> I found and read the relevant parts of the SCSI-2 spec.
> I now have tag queueing working.  I also found the DPO flag
> which helps both cards.  Now the 154x does 1460MB/s (2% isn't
> much, but anything helps.)

Cool.  Patch?

> 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
be something in the DPT documentation that one can do with the 
card that one can't do with a 1540 ( bus on/off? ).  1540 is a
well-developed and understood card, whereas most other stuff
isin't nearly as common.

> David Butler
> gdb@dbSystems.com

Regards,

Eric Dorman
edorman@ucsd.edu




             reply	other threads:[~1998-01-12 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-12 20:38 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 23:17 Eric
1998-01-12 20:52 G.David
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=19980112203856.YMmLmyUHBJfpTZ9BZ6YLzbbYaSgux8XvR34b2iOsp4A@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).