From: Simon Haynes <simon@baydel.com>
To: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: SFFDC and blksize_size
Date: Fri, 7 Nov 2003 13:12:54 +0000 [thread overview]
Message-ID: <37CC93E8710D@baydel.com> (raw)
I have been writing a block driver for SSFDC compliant SMC cards. This stuff
allocates 16k blocks. When I get requests the transfers are split into the
size I specifty in the blksize_size{MAJOR] array. It sems that most things
set this to 1k. In my case this causes a performance problem as I have to
end up doing 16 * (16K write, 16K read, 16k erase) to write and verify a
16k block which has been previously written.
I increased this size to 4k and now I only need 4 * this lot. !deally I would
like to do 1. However if I set the block size to 16k the module installation
crashes when I call register_disk.
I guess I could deal with the request queue myself but I would just like to
know if there is a 4k limit or I have some other bug.
Many Thanks
Simon.
next reply other threads:[~2003-11-07 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 13:12 Simon Haynes [this message]
2003-11-07 14:18 ` SFFDC and blksize_size David Woodhouse
2003-11-10 14:09 ` Jens Axboe
2003-11-10 14:17 ` David Woodhouse
2003-11-10 14:23 ` 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=37CC93E8710D@baydel.com \
--to=simon@baydel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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