All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Konstantin Kletschke <konsti@ludenkalle.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Quick aic7xxx bug hunt...
Date: Mon, 23 Sep 2002 18:18:55 -0400	[thread overview]
Message-ID: <3D8F934F.7000606@mandrakesoft.com> (raw)
In-Reply-To: 2640410816.1032818062@aslan.btc.adaptec.com

Justin T. Gibbs wrote:
> I somewhat doubt that any CPU would hold onto a posted write for 200us
> since you are not guaranteed that a read will occur quickly and you want
> those write buffers to be availble for other clients, but regardless, the
> code has not been as you describe since November of last year.


Great, I stand corrected.  Looks like 2.5 code is ancient then?

comments on the 2.4 code:
* the 1000us delay in ahc_reset needs to be turned into a sleep, instead 
all paths to that function [AFAICS] can sleep.  likewise for the huge 
delay in ahc_acquire_seeprom.

* 400ms worst case udelay() is in ahc_clear_critical_section is kinda 
annoying [but I suppose it can be lived with, if the average is a lot 
less than that :)]

* the delay in ahc_init should be replaced with a sleep

* PCI posting?  (aic7xxx_core.c, line 1322, the last statement in the 
function...)

                 ahc_outb(ahc, CLRINT, CLRSCSIINT);

I'll look it over some more later.


  reply	other threads:[~2002-09-23 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 18:00 2.4.20-pre7-ac3 aic7xxx broken? Konstantin Kletschke
2002-09-23 19:15 ` Justin T. Gibbs
2002-09-23 21:27   ` Quick aic7xxx bug hunt Jeff Garzik
2002-09-23 21:54     ` Justin T. Gibbs
2002-09-23 22:18       ` Jeff Garzik [this message]
2002-09-23 22:44         ` Justin T. Gibbs
2002-09-23 22:50           ` Jeff Garzik
2002-09-23 22:55             ` Justin T. Gibbs
2002-09-23 23:22               ` Jeff Garzik
2002-09-23 23:28                 ` Jeff Garzik
2002-09-23  7:44                   ` Benjamin Herrenschmidt

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=3D8F934F.7000606@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=gibbs@scsiguy.com \
    --cc=konsti@ludenkalle.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.