From: BenHanokh Gabriel <gabriel@SANgate.com>
To: linux-mm@kvack.org
Subject: mix-block size for raw_io ??
Date: Thu, 12 Oct 2000 19:18:49 +0300 [thread overview]
Message-ID: <39E5E469.2020304@SANgate.com> (raw)
hi
i saw that the raw interface is using 1/2K blocks for io.
i understand that raw_io needs to support disk accesses in sector
resolution, but why is it not possible to mix block sizes for the same
device -> giving a much better performance using something like:
---------------------
left_bytes = io_size % 4K
bytes = io_size - left_bytes
call brw_kiovec(bytes) // using_4K_blocks
call brw_kiovec(left_bytes) // using_1/2K_blocks
----------------------
the brw_kiovec() doesn't seems to remember block_size between calls as
it calculates everything based on the block_size passed as parameter.
is there any reason why we don't use mix-block-size ?
please CC me for answers
THX
/Gabriel BenHanokh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next reply other threads:[~2000-10-12 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-12 16:18 BenHanokh Gabriel [this message]
2000-10-12 18:06 ` Stephen Tweedie
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=39E5E469.2020304@SANgate.com \
--to=gabriel@sangate.com \
--cc=linux-mm@kvack.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