From: "Jangsub Yi" <jangsub.yi@samsung.com>
To: "'Christoph Hellwig'" <hch@infradead.org>
Cc: <ulf.hansson@linaro.org>, <linux-mmc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <junwoo80.lee@samsung.com>,
<sh8267.baek@samsung.com>, <wkon.kim@samsung.com>
Subject: RE: [PATCH] mmc: Add config_host callback to set a mmc queue
Date: Mon, 11 Nov 2024 17:06:35 +0900 [thread overview]
Message-ID: <0b2e01db3410$a05f41c0$e11dc540$@samsung.com> (raw)
In-Reply-To: <ZyzYnw0PgpyViFdf@infradead.org>
> On Thu, Nov 07, 2024 at 06:06:11PM +0900, ??? wrote:
> > Currently, there is no way to configure a request queue on the host
side.
> > Although there are various exported symbols in
> > kernel/block/blk-settings.c that can be used to configure a request
> > queue, users cannot utilize them as needed.
>
> If you actually provided a user and didn't just try to offend the kernel
> maintainers by submitting dead code I could explain you in detail why
> youre idea is flawed.
>
If a machine uses both SD and MMC simultaneously, how should timeouts be set
for each? And if different timeout values need to be used depending on the
manufacturer of the SD card, how can this be implemented? I believe it is
not appropriate to make such changes in the core code. There needs to be
a way to configure these settings per host.
next prev parent reply other threads:[~2024-11-11 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241106051403epcas1p29e983006930bd7b8364b1a1f858ad21c@epcas1p2.samsung.com>
2024-11-06 5:13 ` [PATCH] mmc: Add config_host callback to set a mmc queue Jangsub Yi
2024-11-07 6:30 ` Christoph Hellwig
2024-11-07 9:06 ` ???
2024-11-07 15:11 ` 'Christoph Hellwig'
2024-11-11 8:06 ` Jangsub Yi [this message]
2024-12-10 5:23 ` Jangsub Yi
2024-12-10 5:28 ` 'Christoph Hellwig'
2024-12-10 6:20 ` Jangsub Yi
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='0b2e01db3410$a05f41c0$e11dc540$@samsung.com' \
--to=jangsub.yi@samsung.com \
--cc=hch@infradead.org \
--cc=junwoo80.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sh8267.baek@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=wkon.kim@samsung.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