public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Christopher Friesen <cfriesen@nortelnetworks.com>
Cc: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>,
	Fred <fred@arkansaswebs.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Should I use Linux to develop driver for specialized ISA card?
Date: Tue, 04 Sep 2001 12:58:59 -0700	[thread overview]
Message-ID: <3B953283.E925CD72@zip.com.au> (raw)
In-Reply-To: <E15eHup-0003ir-00@the-village.bc.nu> <01090410264000.14864@bits.linuxball> <3B950034.17909E5D@nortelnetworks.com> <200109041823.f84INqE13918@maild.telia.com> <3B952CFE.A3B6FF95@nortelnetworks.com>

Christopher Friesen wrote:
> 
> > 1) Why shouldn't the low-latency patches work for another architecture?
> > Andrew Morton might be interested to fix other architectures too.
> > (but most patches are not in architecture specific code)
> 
> Well, a while back I took a look at the low latency patch and saw a bunch of
> arch-specific files being modified so I assumed that it wouldn't do much on a
> different architecture.  I may have been wrong.  I guess its time for me to do
> some testing.
> 

It is now arch-neutral.   There used to be a couple of x86 tweaks,
but they became unnecessary when some softirq fixes were merged.

So for other architectures the only thing which needs changing
is the actual config entries in arch/<arch>/config.in.  If you
do take a look at this, please send me the diffs for whatever
your architecture is.

I haven't heard much from non-x86 people; there were some remaining
latency problems with PPC many months ago, but they were never
explained and I don't know if the problems remain, or if indeed
they were ever real.

It's kind of amazing that you're seeing 300 millisec stalls on
a system with no local disks - most problems occur in the
VM list walking, dirty buffer writeout, etc.  Unless you're
performing a lot of fileystem work across that FC controller?
It could be that there is an architecture- or driver-specific
problem in your setup.

-

      reply	other threads:[~2001-09-04 19:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-04 12:57 Should I use Linux to develop driver for specialized ISA card? Rastislav Stanik
2001-09-04 13:28 ` Richard B. Johnson
2001-09-04 13:30 ` Anton Altaparmakov
2001-09-04 13:42 ` Erik Mouw
2001-09-17 19:19   ` Rogier Wolff
2001-09-04 15:15 ` Alan Cox
2001-09-04 15:26   ` Fred
2001-09-04 15:36     ` Alan Cox
2001-09-04 15:40     ` Joel Jaeggli
2001-09-04 16:24     ` Christopher Friesen
2001-09-04 17:32       ` Mark Frazer
2001-09-04 17:53         ` Christopher Friesen
2001-09-04 18:19       ` Roger Larsson
2001-09-04 18:54         ` J Sloan
2001-09-04 19:35         ` Christopher Friesen
2001-09-04 19:58           ` Andrew Morton [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=3B953283.E925CD72@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=cfriesen@nortelnetworks.com \
    --cc=fred@arkansaswebs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.larsson@skelleftea.mail.telia.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