From: Lauri Kasanen <cand@gmx.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-mips@vger.kernel.org, tsbogend@alpha.franken.de,
linux-block@vger.kernel.org
Subject: Re: [PATCH 6/6] block: Add n64 cart driver
Date: Mon, 4 Jan 2021 17:56:59 +0200 [thread overview]
Message-ID: <20210104175659.f5433d55d8e41b3c8b620894@gmx.com> (raw)
In-Reply-To: <db1936b0-a1ab-41b3-be09-ec301ea7ebc3@kernel.dk>
On Mon, 4 Jan 2021 08:49:55 -0700
Jens Axboe <axboe@kernel.dk> wrote:
> On 1/4/21 8:43 AM, Lauri Kasanen wrote:
> > On Mon, 4 Jan 2021 08:40:10 -0700
> > Jens Axboe <axboe@kernel.dk> wrote:
> >> It should definitely get reviewed first. One easy question - there's no
> >> commit message in this one. It's a new driver, it should include some
> >> documentation on what it is, etc.
> >
> > It's already had one (rfc) round on linux-mips. Or do you mean by
> > others (who?)
>
> I mean the actual block driver from the block point of view. From
> a quick look, looks like there's no irq or anything, so it's
> strictly polled mode? Probably would make sense to push this out
> of the app path then, by using BLK_MQ_F_BLOCKING.
It's very unclear to me what that flag does. I read all the docs
available, but nothing made it clear (same applies for almost all
BLK_MQ_*).
- Lauri
next prev parent reply other threads:[~2021-01-04 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 13:50 [PATCH 6/6] block: Add n64 cart driver Lauri Kasanen
2021-01-04 15:40 ` Jens Axboe
2021-01-04 15:43 ` Lauri Kasanen
2021-01-04 15:49 ` Jens Axboe
2021-01-04 15:56 ` Lauri Kasanen [this message]
2021-01-04 16:07 ` Jens Axboe
2021-01-04 15:49 ` Keith Busch
2021-01-04 16:01 ` Lauri Kasanen
2021-01-04 16:13 ` Keith Busch
2021-01-04 16:27 ` Lauri Kasanen
2021-01-04 16:28 ` Jens Axboe
2021-01-04 16:42 ` Lauri Kasanen
-- strict thread matches above, loose matches on Subject: below --
2020-12-25 17:01 Lauri Kasanen
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=20210104175659.f5433d55d8e41b3c8b620894@gmx.com \
--to=cand@gmx.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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