linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@cse.unsw.edu.au>
To: bo <bo@sosnetwork.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: resync patch & Neil's recent patches
Date: Sat, 29 Jun 2002 23:02:28 +1000 (EST)	[thread overview]
Message-ID: <15645.45028.216750.35335@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from bo on Friday June 28

On Friday June 28, bo@sosnetwork.net wrote:
> Neil,
> 
> > > I saw some bug fixes and improvement on this topic from
> > >  http://marc.theaimsgroup.com/?l=linux-kernel&m=100876771508736&w=2
> >
> 
> According to log file(from above infor), it cleaned up many things related
> with RESYNC, and had
> some bug fixes. He mentioned it goes to linux2.5.x.
> 
> I think we should have the same changes to Linux 2.4.x, don't you?

I don't think they were significant bugs.  resync works quite well in
2.4.  Well enough that I don't think it should be fiddled with too much.

> If so which release should include them? Any problem to apply this patch
> to my 2.4.5?

They won't work in 2.4 as they stand.  There were some major changes
to the block device layer in 2.5 and these patches require (and are
required by) these changes.

> 
> How about your patches(23+)? Can I apply them to my lINUX2.4.5?

No.  Same reason.  I might back-port the more significant ones, but
much of it was code-cleanliness rather than bug fixes.

> 
> I already use 100M  for speed _limit_min,  300M for speed _limit_max.
> I could not notice a big difference from changing this values.
> 
> Q1: This value go back to the default at boot/reset,  Should I modify to
> change this
>        default value in "md.c"? By any config parameter?

Don't modify md.c.  Just echo a number to the /proc file in a boot
script.

> 
> Q2:  >hdparm -tT /dev/hdxx
>           Timing buffer-cache reads: 52.24 MB/s
>           Timing buffered disk reads: 24.43 MB/s
> 
>         The "resync" speed on the raid1 device with hdxx:  25.4MB/s.
> 
>         Do you think this speed is reasonable enough?

You couldn't ask for better.  This speed looks fine.

NeilBrown

      reply	other threads:[~2002-06-29 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 17:45 Simple question, maybe Jason Shelton
2002-06-26 18:02 ` Neil Brown
2002-06-26 18:05   ` Jason Shelton
2002-06-26 18:17     ` Neil Brown
2002-06-26 22:14       ` resync patch & Neil's recent patches bo
2002-06-28 15:21         ` Neil Brown
2002-06-28 23:46           ` bo
2002-06-29 13:02             ` Neil Brown [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=15645.45028.216750.35335@notabene.cse.unsw.edu.au \
    --to=neilb@cse.unsw.edu.au \
    --cc=bo@sosnetwork.net \
    --cc=linux-raid@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).