From: Pierre Ossman <drzeus@drzeus.cx>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Manuel Lauss <mano@roarinelk.homelinux.net>,
linux-kernel@vger.kernel.org
Subject: Re: MMC layer regression with single-block controllers
Date: Wed, 25 Mar 2009 16:53:28 +0100 [thread overview]
Message-ID: <20090325165328.251daabb@mjolnir.ossman.eu> (raw)
In-Reply-To: <20090325114248.GN27476@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
On Wed, 25 Mar 2009 12:42:48 +0100
Jens Axboe <jens.axboe@oracle.com> wrote:
> On Wed, Mar 25 2009, Pierre Ossman wrote:
> >
> > That's an annoying limitation and sort of defeats the purpose of
> > specifying a maximum sector count. Why can't it go below 8?
>
> Because it would add all sorts of complexity for handling 4kb block size
> file systems on top of the block device. The bio_add_page() api depends
> on being able to add a single page at least, it has to or you would need
> to push that complexity to the callers.
>
Requests going in into the block layer and requests coming out aren't
that strongly coupled, so I don't see it of that much of a stretch to
expect this to be handled.
> So it's annoying, but you have to do the incremental completions
> yourself for the (obscure) device that doesn't do more than 512b
> transfers. It's really not that difficult, and it would be simpler than
> supporting partial completions generically in the block layer.
The code was there previously, but it seemed a bit redundant to have
functionality like that in the block driver since we've already told
the block layer about the restrictions.
The code was pretty simple. Basically it just cropped the sg list at
the correct place. Couldn't that be as easily done in the block layer?
>
> Saying that it defeats the purpose of the setting is missing the bigger
> picture - basically all other devices, that have sane limits (like 128k,
> or whatnot).
>
I suppose. But it makes the feature completely useless for MMC as it
has to implement it's own cropping of requests anyway.
Rgds
--
-- Pierre Ossman
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: 198 bytes --]
next prev parent reply other threads:[~2009-03-25 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 9:28 Manuel Lauss
2009-03-24 20:01 ` Pierre Ossman
2009-03-25 10:48 ` Manuel Lauss
2009-03-25 11:04 ` Jens Axboe
2009-03-25 11:36 ` Pierre Ossman
2009-03-25 11:42 ` Jens Axboe
2009-03-25 15:53 ` Pierre Ossman [this message]
2009-03-25 16:14 ` Jens Axboe
2009-03-25 16:24 ` Pierre Ossman
2009-03-25 17:43 ` 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=20090325165328.251daabb@mjolnir.ossman.eu \
--to=drzeus@drzeus.cx \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mano@roarinelk.homelinux.net \
/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
all inboxes | Powered by JetHome®