All of lore.kernel.org
 help / color / mirror / Atom feed
From: Song Liu <song@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Hans de Goede <hdegoede@redhat.com>,
	Richard Weinberger <richard@nod.at>,
	Minchan Kim <minchan@kernel.org>,
	linux-mtd@lists.infradead.org, dm-devel@redhat.com,
	linux-block@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>,
	drbd-dev@lists.linbit.com,
	linux-raid <linux-raid@vger.kernel.org>,
	Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	cgroups@vger.kernel.org
Subject: Re: [PATCH 05/12] md: update the optimal I/O size on reshape
Date: Fri, 11 Sep 2020 23:17:28 -0700	[thread overview]
Message-ID: <CAPhsuW56nRgq_hAs4zdg+qabVsbyYkmZk2+4+4ykzbg0Aa=W2g@mail.gmail.com> (raw)
In-Reply-To: <20200910144833.742260-6-hch@lst.de>

On Thu, Sep 10, 2020 at 7:48 AM Christoph Hellwig <hch@lst.de> wrote:
>
> The raid5 and raid10 drivers currently update the read-ahead size,
> but not the optimal I/O size on reshape.  To prepare for deriving the
> read-ahead size from the optimal I/O size make sure it is updated
> as well.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Acked-by: Song Liu <song@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Song Liu <song@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-raid <linux-raid@vger.kernel.org>,
	Minchan Kim <minchan@kernel.org>,
	Richard Weinberger <richard@nod.at>,
	open list <linux-kernel@vger.kernel.org>,
	linux-block@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
	dm-devel@redhat.com, linux-mtd@lists.infradead.org,
	Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
	cgroups@vger.kernel.org, Linux-MM <linux-mm@kvack.org>,
	drbd-dev@lists.linbit.com
Subject: Re: [PATCH 05/12] md: update the optimal I/O size on reshape
Date: Fri, 11 Sep 2020 23:17:28 -0700	[thread overview]
Message-ID: <CAPhsuW56nRgq_hAs4zdg+qabVsbyYkmZk2+4+4ykzbg0Aa=W2g@mail.gmail.com> (raw)
In-Reply-To: <20200910144833.742260-6-hch@lst.de>

On Thu, Sep 10, 2020 at 7:48 AM Christoph Hellwig <hch@lst.de> wrote:
>
> The raid5 and raid10 drivers currently update the read-ahead size,
> but not the optimal I/O size on reshape.  To prepare for deriving the
> read-ahead size from the optimal I/O size make sure it is updated
> as well.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Acked-by: Song Liu <song@kernel.org>

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-09-12  6:17 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 14:48 bdi cleanups v4 Christoph Hellwig
2020-09-10 14:48 ` Christoph Hellwig
2020-09-10 14:48 ` Christoph Hellwig
2020-09-10 14:48 ` [PATCH 01/12] fs: remove the unused SB_I_MULTIROOT flag Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:41   ` Jan Kara
2020-09-17  9:41     ` Jan Kara
2020-09-10 14:48 ` [PATCH 02/12] drbd: remove dead code in device_to_statistics Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:46   ` Jan Kara
2020-09-17  9:46     ` Jan Kara
2020-09-17  9:46     ` Jan Kara
2020-09-10 14:48 ` [PATCH 03/12] drbd: remove RB_CONGESTED_REMOTE Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:55   ` Jan Kara
2020-09-17  9:55     ` Jan Kara
2020-09-19  6:58     ` Christoph Hellwig
2020-09-19  6:58       ` Christoph Hellwig
2020-09-19  6:58       ` Christoph Hellwig
2020-09-10 14:48 ` [PATCH 04/12] bdi: initialize ->ra_pages and ->io_pages in bdi_init Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17 10:04   ` Jan Kara
2020-09-17 10:04     ` Jan Kara
2020-09-17 10:04     ` Jan Kara
2020-09-19  7:01     ` Christoph Hellwig
2020-09-19  7:01       ` Christoph Hellwig
2020-09-10 14:48 ` [PATCH 05/12] md: update the optimal I/O size on reshape Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-12  6:17   ` Song Liu [this message]
2020-09-12  6:17     ` Song Liu
2020-09-12  6:17     ` Song Liu
2020-09-10 14:48 ` [PATCH 06/12] block: lift setting the readahead size into the block layer Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17 10:35   ` Jan Kara
2020-09-17 10:35     ` Jan Kara
2020-09-17 10:35     ` Jan Kara
2020-09-19  7:31     ` Christoph Hellwig
2020-09-19  7:31       ` Christoph Hellwig
2020-09-10 14:48 ` [PATCH 07/12] bdi: remove BDI_CAP_CGROUP_WRITEBACK Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-16  9:28   ` David Sterba
2020-09-16  9:28     ` David Sterba
2020-09-16  9:28     ` David Sterba
2020-09-17  9:36   ` Jan Kara
2020-09-17  9:36     ` Jan Kara
2020-09-17  9:36     ` Jan Kara
2020-09-10 14:48 ` [PATCH 08/12] bdi: remove BDI_CAP_SYNCHRONOUS_IO Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:36   ` Jan Kara
2020-09-17  9:36     ` Jan Kara
2020-09-17  9:36     ` Jan Kara
2020-09-10 14:48 ` [PATCH 09/12] mm: use SWP_SYNCHRONOUS_IO more intelligently Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:06   ` Jan Kara
2020-09-17  9:06     ` Jan Kara
2020-09-10 14:48 ` [PATCH 10/12] bdi: replace BDI_CAP_STABLE_WRITES with a queue and a sb flag Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:25   ` Jan Kara
2020-09-17  9:25     ` Jan Kara
2020-09-19  6:51     ` Christoph Hellwig
2020-09-19  6:51       ` Christoph Hellwig
2020-09-19  6:51       ` Christoph Hellwig
2020-09-10 14:48 ` [PATCH 11/12] bdi: invert BDI_CAP_NO_ACCT_WB Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:27   ` Jan Kara
2020-09-17  9:27     ` Jan Kara
2020-09-17  9:27     ` Jan Kara
2020-09-10 14:48 ` [PATCH 12/12] bdi: replace BDI_CAP_NO_{WRITEBACK,ACCT_DIRTY} with a single flag Christoph Hellwig
2020-09-10 14:48   ` [PATCH 12/12] bdi: replace BDI_CAP_NO_{WRITEBACK, ACCT_DIRTY} " Christoph Hellwig
2020-09-10 14:48   ` Christoph Hellwig
2020-09-17  9:31   ` [PATCH 12/12] bdi: replace BDI_CAP_NO_{WRITEBACK,ACCT_DIRTY} " Jan Kara
2020-09-17  9:31     ` [PATCH 12/12] bdi: replace BDI_CAP_NO_{WRITEBACK, ACCT_DIRTY} " Jan Kara
2020-09-17  9:31     ` [PATCH 12/12] bdi: replace BDI_CAP_NO_{WRITEBACK,ACCT_DIRTY} " Jan Kara
2020-09-15 15:18 bdi cleanups v5 Christoph Hellwig
2020-09-15 15:18 ` [PATCH 05/12] md: update the optimal I/O size on reshape Christoph Hellwig
2020-09-15 15:18   ` Christoph Hellwig
2020-09-15 15:18   ` Christoph Hellwig

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='CAPhsuW56nRgq_hAs4zdg+qabVsbyYkmZk2+4+4ykzbg0Aa=W2g@mail.gmail.com' \
    --to=song@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=dm-devel@redhat.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=hch@lst.de \
    --cc=hdegoede@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.