linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "John Stoffel" <stoffel@lucent.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm2
Date: Fri, 30 May 2003 16:56:16 -0400	[thread overview]
Message-ID: <16087.50544.283105.222031@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030530133015.4f305808.akpm@digeo.com>

>> Any hint on when -mm3 will be out,

Andrew> About ten hours hence, probably.

Great, I'll take a look for it tomorrow morning if I'm lucky.

>> and if it will include the RAID1 patches?

Andrew> I have a raid0 patch from Neil, but no raid1 patch.  I saw one
Andrew> drift past, from Zwane (I think), but wasn't sure that it
Andrew> worked.  If someone has a raid1 fix, please send it.

Hmmm... I could have sworn that Neil sent a RAID1 patch out as well,
which was just adding an 'else' after a block.  Here it is:

 ----------- Diffstat output ------------
 ./drivers/md/raid1.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff ./drivers/md/raid1.c~current~ ./drivers/md/raid1.c
--- ./drivers/md/raid1.c~current~	2003-05-29 11:05:03.000000000 +1000
+++ ./drivers/md/raid1.c	2003-05-29 11:05:08.000000000 +1000
@@ -137,7 +137,7 @@ static void put_all_bios(conf_t *conf, r
 			BUG();
 		bio_put(r1_bio->read_bio);
 		r1_bio->read_bio = NULL;
-	}
+	} else
 	for (i = 0; i < conf->raid_disks; i++) {
 		struct bio **bio = r1_bio->write_bios + i;
 		if (*bio) {

Andrew> Welll ext3 has been a bit bumpy of course.  It's getting
Andrew> better, but I haven't yet been able to give it a 12-hour bash
Andrew> on the 4-way.  Last time I tried a circuit breaker conked; it
Andrew> lasted three hours but even ext3 needs electricity.  But three
Andrew> hours is very positive - it was hard testing.

I've got a dual PIII 550 with 8 disks on it, so I'll see about beating
on it if I get a change.  I need to take a backup anyway this
weekend... 

Andrew> I'm not testing RAID at present, partly because I'm too
Andrew> stoopid to understand mdadm and partly because the
Andrew> box-with-18-disks heats the room up too much.  This needs to
Andrew> change, because of possible interaction between the IO
Andrew> scheduler work and software RAID.

The mdadm is alot better than the old raid stuff for sure.  

Once I get 2.5.70* up and running, I'll try out my hacks to the
Cyclades driver (and we need a patch for the Kconfig entry as well,
it's wrong in it's description) under ISA to see if I can get it
working.  I'll bounce those to you and Linus if they fly. 

Thanks,
John
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-05-30 20:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29  8:29 2.5.70-mm2 Andrew Morton
2003-05-29  8:49 ` 2.5.70-mm2 Andrew Morton
2003-05-29 11:23 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:05   ` 2.5.70-mm2 John Stoffel
2003-05-30 20:30     ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:56       ` John Stoffel [this message]
2003-05-30 22:36       ` 2.5.70-mm2 Mingming Cao
2003-05-29 12:55 ` 2.5.70-mm2 still dies with RAID-1 Helge Hafting
2003-05-29 21:52 ` 2.5.70-mm2 Badari Pulavarty
2003-05-30 11:17   ` 2.5.70-mm2 Andrew Morton
2003-05-29 16:48 2.5.70-mm2 Downing, Thomas
2003-05-29 17:36 ` 2.5.70-mm2 Andrew Morton
2003-05-29 21:22   ` 2.5.70-mm2 John Stoffel
2003-05-29 21:35     ` 2.5.70-mm2 Andrew Morton
2003-05-29 20:08 ` 2.5.70-mm2 Paul Larson
2003-05-29 19:08 2.5.70-mm2 Downing, Thomas

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=16087.50544.283105.222031@gargle.gargle.HOWL \
    --to=stoffel@lucent.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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