From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Luis Chamberlain <mcgrof@kernel.org>,
Sandeep Dhavale <dhavale@google.com>,
Juan Yescas <jyescas@google.com>
Subject: Re: [PATCH v6 0/8] Support limits below the page size
Date: Fri, 16 Jun 2023 09:02:37 +0200 [thread overview]
Message-ID: <20230616070237.GC29500@lst.de> (raw)
In-Reply-To: <1d55e942-5150-de4c-3a02-c3d066f87028@acm.org>
On Thu, Jun 15, 2023 at 06:55:36AM -0700, Bart Van Assche wrote:
> On 6/14/23 21:15, Christoph Hellwig wrote:
>> I really hate having this core complexity, but I suspect trying to driver
>> hacks would be even worse than that, especially as this goes through
>> the SCSI midlayer. I think the answer is simply that if Google keeps
>> buying broken hardware for their products from Samsung they just need
>> to stick to a 4k page size instead of moving to a larger one.
>
> Although I do not like it that the Exynos UFS controller does not follow
> the UFS standard, this UFS controller is used much more widely than only in
> devices produced by my employer. See e.g. the output of the following grep
> command:
But it seems like no one is insisting on using it with larger than 4k
page sizes. I think we should just prohibit using the driver for those
kernel configs and be done with it.
next prev parent reply other threads:[~2023-06-16 7:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 20:33 [PATCH v6 0/8] Support limits below the page size Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 1/8] block: Use pr_info() instead of printk(KERN_INFO ...) Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 2/8] block: Prepare for supporting sub-page limits Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 3/8] block: Support configuring limits below the page size Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 4/8] block: Make sub_page_limit_queues available in debugfs Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 5/8] block: Support submitting passthrough requests with small segments Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 6/8] block: Add support for filesystem requests and " Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 7/8] scsi_debug: Support configuring the maximum segment size Bart Van Assche
2023-06-12 20:33 ` [PATCH v6 8/8] null_blk: " Bart Van Assche
2023-06-12 22:17 ` Damien Le Moal
2023-06-13 0:44 ` Bart Van Assche
2023-06-13 6:47 ` Damien Le Moal
2023-06-13 6:52 ` Christoph Hellwig
2023-06-15 2:01 ` [PATCH v6 0/8] Support limits below the page size Bart Van Assche
2023-06-15 2:22 ` Jens Axboe
2023-06-15 4:15 ` Christoph Hellwig
2023-06-15 13:55 ` Bart Van Assche
2023-06-16 7:02 ` Christoph Hellwig [this message]
2023-06-16 20:26 ` Bart Van Assche
2023-06-16 21:48 ` Jens Axboe
2023-06-16 22:28 ` Bart Van Assche
2023-08-04 23:11 ` Juan Yescas
2023-06-15 14:16 ` Jens Axboe
2023-06-15 14:16 ` Bart Van Assche
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=20230616070237.GC29500@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dhavale@google.com \
--cc=jyescas@google.com \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@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.