From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 0/2] Two loop driver patches
Date: Mon, 2 Aug 2021 17:01:58 -0700 [thread overview]
Message-ID: <20210803000200.4125318-1-bvanassche@acm.org> (raw)
Hi Jens,
The two patches in this patch series are what I came up with while testing
Android software. Please consider these patches for inclusion in the upstream
kernel.
Thanks,
Bart.
Bart Van Assche (2):
loop: Prevent that an I/O scheduler is assigned
loop: Add the default_queue_depth kernel module parameter
drivers/block/loop.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
next reply other threads:[~2021-08-03 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 0:01 Bart Van Assche [this message]
2021-08-03 0:01 ` [PATCH 1/2] loop: Prevent that an I/O scheduler is assigned Bart Van Assche
2021-08-03 1:54 ` Ming Lei
2021-08-03 5:23 ` Bart Van Assche
2021-08-03 7:18 ` Ming Lei
2021-08-03 0:02 ` [PATCH 2/2] loop: Add the default_queue_depth kernel module parameter Bart Van Assche
2021-08-03 1:57 ` Ming Lei
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=20210803000200.4125318-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).