From: viro@parcelfarce.linux.theplanet.co.uk
To: Szakacsits Szabolcs <szaka@sienet.hu>
Cc: Andries Brouwer <aebr@win.tue.nl>,
fledely <fledely@bgumail.bgu.ac.il>,
linux-ntfs-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Accessing odd last partition sector (was: [Linux-NTFS-Dev] mkntfs dirty volume marking)
Date: Sat, 10 Apr 2004 23:55:14 +0100 [thread overview]
Message-ID: <20040410225514.GX31500@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0404102352520.840-100000@mlf.linux.rulez.org>
On Sun, Apr 11, 2004 at 12:23:47AM +0200, Szakacsits Szabolcs wrote:
> Just one question, in the most common cases the block size ends up between
> 512 and 4096 bytes. Depending on how this block size used, it can have a
> significant impact on performance (e.g. 512 vs 4096). Is this true or is
> it used to be performance independent?
Resulting requests are immediately merged anyway. Yes, we get more bio
sitting on top of the merged request; however, it's heavily IO-dominated
and I would be surprised if you really saw any noticable overhead in that
situation.
next prev parent reply other threads:[~2004-04-10 22:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001601c41db7$aa0a02e0$0100000a@p667>
2004-04-09 11:38 ` Szakacsits Szabolcs
2004-04-10 20:29 ` Andries Brouwer
2004-04-10 20:54 ` viro
2004-04-10 21:04 ` Szakacsits Szabolcs
2004-04-10 21:13 ` viro
2004-04-10 22:23 ` Szakacsits Szabolcs
2004-04-10 22:55 ` viro [this message]
2004-04-10 23:14 ` Szakacsits Szabolcs
2004-04-16 13:26 ` Szakacsits Szabolcs
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=20040410225514.GX31500@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=aebr@win.tue.nl \
--cc=fledely@bgumail.bgu.ac.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=szaka@sienet.hu \
/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®