linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Xiao Ni <xni@redhat.com>
Cc: linux-raid@vger.kernel.org, Jes Sorensen <jes.sorensen@redhat.com>
Subject: Re: One patch just review the code
Date: Thu, 7 Aug 2014 20:26:05 +1000	[thread overview]
Message-ID: <20140807202605.4e6a2b1e@notabene.brown> (raw)
In-Reply-To: <835401588.19232017.1407405979159.JavaMail.zimbra@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3546 bytes --]

On Thu, 7 Aug 2014 06:06:19 -0400 (EDT) Xiao Ni <xni@redhat.com> wrote:

> 
> 
> ----- Original Message -----
> > From: "NeilBrown" <neilb@suse.de>
> > To: "Xiao Ni" <xni@redhat.com>
> > Cc: linux-raid@vger.kernel.org, "Jes Sorensen" <jes.sorensen@redhat.com>
> > Sent: Wednesday, August 6, 2014 2:44:20 PM
> > Subject: Re: One patch just review the code
> > 
> > On Tue, 5 Aug 2014 03:12:07 -0400 (EDT) Xiao Ni <xni@redhat.com> wrote:
> > 
> > > Hi all
> > > 
> > >    I'm reading the code of md. I find there is a problem. I know now there
> > >    are arrays mark[SYNC_MARKS] mark_cnt[SYNC_MARKS]
> > > store the information about how many sectors finish recovery and the
> > > moment.
> > > 
> > > 
> > > 7825       currspeed = ((unsigned
> > > long)(io_sectors-mddev->resync_mark_cnt))/2
> > > 7826          /((jiffies-mddev->resync_mark)/HZ +1) +1;
> > >   
> > >    But when calculate the speed of recovery, the sectors used to calculate
> > >    contains
> > > the sectors which are not finished recovery.
> > > 
> > >    When assign value to mark_cnt[next], it subtract the sectors which don't
> > >    finish recovery.
> > > So I think when calculate the recovery speed we should subtract the sectors
> > > not finishing
> > > recovery too.
> > > 
> > > 7638          mark_cnt[next] = io_sectors -
> > > atomic_read(&mddev->recovery_active);
> > > 
> > >    So I try to modify and the patch is:
> > > 
> > > --- linux-stable/drivers/md/md.c 2014-07-30 14:36:37.327535805 +0800
> > > +++ fix/md.c   2014-07-31 16:40:57.151493177 +0800
> > > @@ -7652,7 +7652,7 @@
> > >        */
> > >       cond_resched();
> > >  
> > > -     currspeed = ((unsigned long)(io_sectors-mddev->resync_mark_cnt))/2
> > > +     currspeed = ((unsigned
> > > long)(io_sectors-atomic_read(&mddev->recovery_active)-mddev->resync_mark_cnt))/2
> > >          /((jiffies-mddev->resync_mark)/HZ +1) +1;
> > >  
> > >       if (currspeed > speed_min(mddev)) {
> > > 
> > >    Am I right?
> > 
> > Yes, that looks right.
> > If you create a properly formatted patch, and wrap that long line nicely I'll
> > apply it.
> > 
> > Thanks,
> > NeilBrown
> > 
> 
> I definite a new variable, do you allow me to do by this way?

Certainly, nothing wrong with a new variable.

But when you post a patch, please create a new email message with a short
description of the patch as the subject, any extra details or explanation in
the body, then the signed-off-by line and the patch. Then I can just apply
that email without editing it.

Thanks,
NeilBrown

> 
> Signed-off-by: Xiao Ni <xni@redhat.com>
> 
> diff -urN linux-stable/drivers/md/md.c fix/md.c
> --- linux-stable/drivers/md/md.c 2014-07-30 14:36:37.327535805 +0800
> +++ fix/md.c   2014-08-07 16:07:12.559503942 +0800
> @@ -7376,7 +7376,7 @@
>    struct mddev *mddev2;
>    unsigned int currspeed = 0,
>        window;
> -  sector_t max_sectors,j, io_sectors;
> +  sector_t max_sectors,j, io_sectors, recovery_done;
>    unsigned long mark[SYNC_MARKS];
>    unsigned long update_time;
>    sector_t mark_cnt[SYNC_MARKS];
> @@ -7652,7 +7652,8 @@
>        */  
>       cond_resched();
>  
> -     currspeed = ((unsigned long)(io_sectors-mddev->resync_mark_cnt))/2
> +     recovery_done = io_sectors - atomic_read(&mddev->recovery_active);
> +     currspeed = ((unsigned long)recovery_done - mddev->resync_mark_cnt)/2 
>          /((jiffies-mddev->resync_mark)/HZ +1) +1; 
>  
>       if (currspeed > speed_min(mddev)) {


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2014-08-07 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <705044700.17914512.1407222497904.JavaMail.zimbra@redhat.com>
2014-08-05  7:12 ` One patch just review the code Xiao Ni
2014-08-06  6:44   ` NeilBrown
2014-08-07 10:06     ` Xiao Ni
2014-08-07 10:26       ` NeilBrown [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=20140807202605.4e6a2b1e@notabene.brown \
    --to=neilb@suse.de \
    --cc=jes.sorensen@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=xni@redhat.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;
as well as URLs for NNTP newsgroup(s).