public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Yu Kuai <yukuai@fnnas.com>
Cc: Christoph Hellwig <hch@infradead.org>, Coly Li <colyli@fnnas.com>,
	linux-raid@vger.kernel.org, linan122@huawei.com, xni@redhat.com,
	dan.carpenter@linaro.org
Subject: Re: [PATCH v5 12/12] md: fix abnormal io_opt from member disks
Date: Mon, 19 Jan 2026 00:36:01 -0800	[thread overview]
Message-ID: <aW3s8cDfbFQrm6gD@infradead.org> (raw)
In-Reply-To: <9642ed5f-1e60-47dd-a333-abc5cb26ebe1@fnnas.com>

On Mon, Jan 19, 2026 at 03:24:19PM +0800, Yu Kuai wrote:
> >> E.g. a spinning hard drive connect to this HBA card reports its max_sectors as 32767 sectors.
> >> This is around 16MB and too large for normal hard drive.
> > Which is larger than what we'd expect for the HDD itself, where it
> > should be around 1MB.  But HBAs do weird stuff, so it might actually
> > be correct here.  Have you talked to the mpt3sas maintainers?
> 
> We CC them in several previous threads, however, they're not responding. :(

In that case we'll have to assume the value is intended.  Especially
if the HBA is running in RAID mode, which would be only sensible path
to modify this value anyway.


  reply	other threads:[~2026-01-19  8:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 17:12 [PATCH v5 00/12] md: align bio to io_opt for better performance Yu Kuai
2026-01-14 17:12 ` [PATCH v5 01/12] md/raid5: fix raid5_run() to return error when log_init() fails Yu Kuai
2026-01-15  1:28   ` Li Nan
2026-01-15  2:29   ` Xiao Ni
2026-01-16 15:05   ` Christoph Hellwig
2026-01-14 17:12 ` [PATCH v5 02/12] md: merge mddev has_superblock into mddev_flags Yu Kuai
2026-01-16 15:06   ` Christoph Hellwig
2026-01-18 11:30     ` Yu Kuai
2026-01-14 17:12 ` [PATCH v5 03/12] md: merge mddev faillast_dev " Yu Kuai
2026-01-14 17:12 ` [PATCH v5 04/12] md: merge mddev serialize_policy " Yu Kuai
2026-01-14 17:12 ` [PATCH v5 05/12] md/raid5: use mempool to allocate stripe_request_ctx Yu Kuai
2026-01-14 17:12 ` [PATCH v5 06/12] md/raid5: make sure max_sectors is not less than io_opt Yu Kuai
2026-01-14 17:12 ` [PATCH v5 07/12] md: support to align bio to limits Yu Kuai
2026-01-16 15:08   ` Christoph Hellwig
2026-01-18 11:40     ` Yu Kuai
2026-01-19  6:47       ` Christoph Hellwig
2026-01-19  7:21         ` Yu Kuai
2026-01-19  7:27           ` Christoph Hellwig
2026-01-19  7:43             ` Yu Kuai
2026-01-19  8:27               ` Christoph Hellwig
2026-01-19  9:15                 ` Yu Kuai
2026-01-14 17:12 ` [PATCH v5 08/12] md: add a helper md_config_align_limits() Yu Kuai
2026-01-14 17:12 ` [PATCH v5 09/12] md/raid5: align bio to io_opt Yu Kuai
2026-01-14 17:12 ` [PATCH v5 10/12] md/raid10: " Yu Kuai
2026-01-14 17:12 ` [PATCH v5 11/12] md/raid0: " Yu Kuai
2026-01-14 17:12 ` [PATCH v5 12/12] md: fix abnormal io_opt from member disks Yu Kuai
2026-01-16 15:08   ` Christoph Hellwig
2026-01-17  3:28     ` Coly Li
2026-01-19  6:48       ` Christoph Hellwig
2026-01-19  7:24         ` Yu Kuai
2026-01-19  8:36           ` Christoph Hellwig [this message]
2026-01-15 23:38 ` [PATCH v5 00/12] md: align bio to io_opt for better performance John Stoffel

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=aW3s8cDfbFQrm6gD@infradead.org \
    --to=hch@infradead.org \
    --cc=colyli@fnnas.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linan122@huawei.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=xni@redhat.com \
    --cc=yukuai@fnnas.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