From: "Sven Köhler" <skoehler@upb.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [blockdevices/NBD] huge read/write-operations are splitted by the kernel
Date: Mon, 08 Sep 2003 15:26:01 +0200 [thread overview]
Message-ID: <bji001$sop$1@sea.gmane.org> (raw)
In-Reply-To: <20030908085802.GH840@suse.de>
> You'll probably find that if you bump the max_sectors count if your
> drive to 256 from 255 (that is the default if you haven't set it), then
> you'll see 128kb chunks all the time.
>
> See max_sectors[] array.
To make it clear:
the kernel will never read or write more sectors at once than specified
in the max_sectors array (where every device has its own value), right?
next prev parent reply other threads:[~2003-09-08 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 0:02 [blockdevices/NBD] huge read/write-operations are splitted by the kernel Sven Köhler
2003-09-08 8:58 ` Jens Axboe
2003-09-08 12:42 ` Sven Köhler
2003-09-08 14:33 ` Jens Axboe
2003-09-08 13:26 ` Sven Köhler [this message]
2003-09-08 14:34 ` 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='bji001$sop$1@sea.gmane.org' \
--to=skoehler@upb.de \
--cc=linux-kernel@vger.kernel.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