From: Randolph Chung <tausq@debian.org>
To: Heikki Hannikainen <hessu@hes.iki.fi>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] K380 partial success, the state of the port?
Date: Wed, 28 Jan 2004 10:15:11 -0800 [thread overview]
Message-ID: <20040128181511.GD959@tausq.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0401281500300.14924@jazz.he.fi>
> Is the parisc port supposed to be this slow at it's current state, or is
> this a problem which is specific to my setup?
fork/exec is very slow on parisc right now. in other areas though
performance is not too shabby. Ryan posted lmbench results to the list
recently. Check the archive for details.
> - Should I go to the 2.6 tree? I compiled it from the CVS (to get the
> tulip driver working) but the SCSI failed:
Yes, you should go to 2.6, but as Joel pointed out SMP is not yet
working correctly.
We have a few scsi gurus on the parisc list so they can address the scsi
issues :)
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2004-01-28 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 14:13 [parisc-linux] K380 partial success, the state of the port? Heikki Hannikainen
2004-01-28 14:52 ` Joel Soete
2004-01-28 18:15 ` Randolph Chung [this message]
2004-01-29 10:03 ` Heikki Hannikainen
2004-01-29 10:15 ` Ryan Bradetich
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=20040128181511.GD959@tausq.org \
--to=tausq@debian.org \
--cc=hessu@hes.iki.fi \
--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