Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@puffin.external.hp.com>
To: Daniel Engstrom <5116@telia.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] New 53c700 driver preformance evaluation
Date: Tue, 23 Oct 2001 23:48:22 -0600	[thread overview]
Message-ID: <200110240548.XAA19760@puffin.external.hp.com> (raw)
In-Reply-To: Message from Daniel Engstrom <5116@telia.com> of "Wed, 24 Oct 2001 07:21:02 +0200." <20011024072102.D1650@zaphod.halden.lillfab.se>

Daniel Engstrom wrote:
> Which is what I saw even if it was not very clearly expressed.
> I got ~400k/s better block throughput with the old driver with disconnects
> disabled (due to some driver problem) than with the new driver.

ah ok. It wasn't obvious to me.

> > BTW, another HPUX (only on workstations) thing is to set WCE (write
> > cache enable) on the SCSI device. 
> Can this behaviur be controlled? I use 10.20.

yes. iirc, it via scsictl command.

# scsictl
Usage: scsictl [-akq] [-m mode[=value]]... [-c command]... device

But HPUX calls WCE something else: "Immediate Reporting".
Keep that in mind when reading the man page.

> Another thing which I want to bring up is locking. It seems out getc() perfor
>   mance is stuck at 314chars/sec while HPUX gives almost 600, could it be
> that HPUX lock primitive is twice as fast as ours?

I think the lock primitive is the same - it's "ldcw".
It's something in the libc/syscall path but I have no clue what.

grant

      reply	other threads:[~2001-10-24  5:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-21 14:19 [parisc-linux] New 53c700 driver preformance evaluation Daniel Engstrom
2001-10-22 17:52 ` Grant Grundler
2001-10-24  5:21   ` Daniel Engstrom
2001-10-24  5:48     ` Grant Grundler [this message]

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=200110240548.XAA19760@puffin.external.hp.com \
    --to=grundler@puffin.external.hp.com \
    --cc=5116@telia.com \
    --cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox