All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: "Jens Stutte (Archiv)" <jens@chianterastutte.eu>,
	Ming Lei <ming.lei@redhat.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: song@kernel.org, linux-raid@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] raid1: ensure bio doesn't have more than BIO_MAX_VECS sectors
Date: Sun, 26 Sep 2021 07:02:43 +0800	[thread overview]
Message-ID: <fd77ff25-4b08-11b8-2e67-7cec988ce834@linux.dev> (raw)
In-Reply-To: <cc91ef81-bf25-cee6-018f-2f79c7a183ae@chianterastutte.eu>



On 9/24/21 11:34 PM, Jens Stutte (Archiv) wrote:
> Hi all,
>
> I just had the occasion to test the new patch as landed in arch linux 
> 5.14.7. Unfortunately it does not work for me. Attached you can find a 
> modification that works for me, though I am not really sure why 
> write_behind seems not to be set to true on my configuration. If there 
> is any more data I can provide to help you to investigate, please let 
> me know.

Thanks for the report!  As commented in bugzilla, this is because 
write-behind
IO still happens even without write-mostly device. I will send new patch 
after
you confirm it works.


1. https://bugzilla.kernel.org/show_bug.cgi?id=213181

Thanks,
Guoqing

  reply	other threads:[~2021-09-25 23:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  6:05 [PATCH] raid1: ensure bio doesn't have more than BIO_MAX_VECS sectors Guoqing Jiang
2021-08-13  7:49 ` Christoph Hellwig
2021-08-13  8:38   ` Guoqing Jiang
2021-08-14  7:55     ` Christoph Hellwig
2021-08-14  8:57       ` Ming Lei
2021-08-16  6:27         ` Guoqing Jiang
2021-08-16  7:13           ` Ming Lei
2021-08-16  9:37         ` Christoph Hellwig
2021-08-16 11:40           ` Ming Lei
2021-08-17  5:06             ` Christoph Hellwig
2021-08-17 12:32               ` Ming Lei
2021-09-24 15:34                 ` Jens Stutte (Archiv)
2021-09-25 23:02                   ` Guoqing Jiang [this message]
2021-08-13  9:27 ` kernel test robot
2021-08-13  9:27   ` kernel test robot
2021-08-13 10:12 ` kernel test robot
2021-08-13 10:12   ` kernel test robot

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=fd77ff25-4b08-11b8-2e67-7cec988ce834@linux.dev \
    --to=guoqing.jiang@linux.dev \
    --cc=hch@infradead.org \
    --cc=jens@chianterastutte.eu \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=song@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 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.