mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: NeilBrown <neilb@suse.de>
Cc: Nicholas Krause <xerofoify@gmail.com>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers:md: Remove no longer needed fixme comment in raid5.c
Date: Wed, 17 Dec 2014 23:44:23 -0500	[thread overview]
Message-ID: <4371.1418877863@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 18 Dec 2014 10:19:06 +1100." <20141218101906.55b7772d@notabene.brown>

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

On Thu, 18 Dec 2014 10:19:06 +1100, NeilBrown said:
> On Wed, 17 Dec 2014 10:49:33 -0500 Nicholas Krause <xerofoify@gmail.com> wrote:
>
> > Removes the no longer needed fix me comment related to not needing the agrument faster for the function,
> > sync_request. Due to getting warnings when building without the agrument it seems that this fix me was
> > wrong and we must keep this agrument in order to avoid build warnings when building without it.

Examining raid1.c, which *does* use the go_faster parameter, I suspect
that the *real* meaning of the FIXME is that the code in raid5.c *should*
possibly be doing this that's done in raid1.c's sync_request():

        /*
         * If there is non-resync activity waiting for a turn,
         * and resync is going fast enough,
         * then let it though before starting on this new sync request.
         */
        if (!go_faster && conf->nr_waiting)
                msleep_interruptible(1000);

(Which is one of the few flow differences for the sync_request() code
in raid1.c versus raid5.c.  I'll however defer to actual RAID experts
on whether raid5 needs resync throttling, or if it's accomplished via
other means I'm not spotting.  Finding a FIXME outside of drivers/staging
is usually a "Here be fearsome and nasty dragons" comment....


[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

      reply	other threads:[~2014-12-18  4:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1418831373-18415-1-git-send-email-xerofoify@gmail.com>
2014-12-17 23:19 ` NeilBrown
2014-12-18  4:44   ` Valdis.Kletnieks [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=4371.1418877863@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=xerofoify@gmail.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

all inboxes | Powered by JetHome®