From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Jens Axboe <axboe@kernel.dk>
Cc: Alex Dubov <oakad@yahoo.com>, LKML <linux-kernel@vger.kernel.org>
Subject: can block drivers get non-fs requests?
Date: Thu, 14 Aug 2008 13:38:10 +0200 [thread overview]
Message-ID: <20080814133810.746751cf@mjolnir.drzeus.cx> (raw)
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Hi Jens,
There is one part of the block layer I'm having trouble completely
understanding (well there are loads really, but right now there's one in
particular :)):
Do block drivers need to watch out for requests that aren't "normal"
reads and writes? The MMC block driver has a funky prepare function
that checks for FS and PC requests and discards anything else. I
believe this is wrong in two regards:
a) PC requests seem to be prepared SCSI cmds, and the MMC driver just
expects normal transfer requests. Therefore, such requests should not
be accepted by this driver.
b) The block layer won't throw weird stuff at us unless explicitly told
so. I.e. a normal block queue will only produce normal FS requests.
Please educate the masses. :)
(I've cc:d Alex as he copied the MMC block driver for the MemoryStick
code, so he's probably also interested in this)
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-08-14 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 11:38 Pierre Ossman [this message]
2008-08-14 11:42 ` can block drivers get non-fs requests? Jens Axboe
2008-08-14 12:39 ` Pierre Ossman
2008-08-14 14:06 ` Jens Axboe
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=20080814133810.746751cf@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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