From: "J.A. Magallon" <jamagallon@able.es>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21rc8aa1
Date: Sat, 28 Jun 2003 03:34:35 +0200 [thread overview]
Message-ID: <20030628013435.GG9706@werewolf.able.es> (raw)
In-Reply-To: <20030612032021.GB1571@dualathlon.random>; from andrea@suse.de on Thu, Jun 12, 2003 at 05:20:21 +0200
Hi,
On 06.12, Andrea Arcangeli wrote:
> This version has some experimental change to the blkdev layer (latency
> fixes from Chris and Nick too plus the backout of the rc6 latency change
> to see if we can fix it w/o generating overscheduling, especially
> because it doesn't sound the right fix), so I would recommend some
> beating before doing anything critical with it. I would expect it as
> worse to deadlock with some task in D state. It worked fine for me so
> far but I didn't run big stress yet. In theory it should be better, but
> I just wanted to give a warning until it is better tested ;).
>
> URL:
>
> http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.21rc8aa1.gz
> http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.21rc8aa1/
>
In sg.c, gcc shouts on:
PRINT_PROC("%u\t%hu\t%hd\t%hu\t%d\t%d\n",
shp->unique_id, shp->host_busy, shp->cmd_per_lun,
shp->sg_tablesize, (int)shp->unchecked_isa_dma,
(int)shp->hostt->emulated);
shp->host_busy should be accessed through atomic_read(), I think.
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.21-jam1 (gcc 3.3 (Mandrake Linux 9.2 3.3-2mdk))
next prev parent reply other threads:[~2003-06-28 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 3:20 2.4.21rc8aa1 Andrea Arcangeli
2003-06-28 1:34 ` J.A. Magallon [this message]
2003-06-28 1:47 ` 2.4.21rc8aa1 Andrea Arcangeli
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=20030628013435.GG9706@werewolf.able.es \
--to=jamagallon@able.es \
--cc=andrea@suse.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 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).