From: Jeff Garzik <jgarzik@pobox.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Merging fails reading /dev/uba1
Date: Mon, 21 Feb 2005 13:31:39 -0500 [thread overview]
Message-ID: <20050221183139.GA5020@havoc.gtf.org> (raw)
In-Reply-To: <20050221102431.64de6c6c@localhost.localdomain>
On Mon, Feb 21, 2005 at 10:24:31AM -0800, Pete Zaitcev wrote:
> On Mon, 21 Feb 2005 08:51:32 +0100, Jens Axboe <axboe@suse.de> wrote:
>
> > > [root@lembas ~]# time dd if=/dev/uba of=/dev/null bs=10k count=10240
> > > real 0m22.731s
>
> > > [root@lembas ~]# time dd if=/dev/uba1 of=/dev/null bs=10k count=10240
> > > real 1m42.622s
>
> > > So, reading from a partition of the same device is 5 times slower than
> > > reading from the device itself. The question is, why?
>
> > I can't explain why the replugging slows it down, maybe you were lucky
> > to get contigious pages in the first case? As far as I can see, ub
> > effectively disables merging by setting max hw/phys segment limit of 1.
>
> If you mean physical replugging, it has nothing to do with the issue.
> I only mentioned it to show that old pages were purged.
>
> Contiguous pages have nothing to do with it either. I forgot to mention
> that in the first case (whole device), all reads are done with length of
> 4KB, while in the second case (partition), all reads are 512 bytes long.
>
> Basically, the key is reading from a partition or not. It causes the
> sub-page sized merging to fail.
Does setting the blkdev's block size change things?
Jeff
next prev parent reply other threads:[~2005-02-21 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 4:00 Pete Zaitcev
2005-02-21 7:51 ` Jens Axboe
2005-02-21 18:24 ` Pete Zaitcev
2005-02-21 18:31 ` Jeff Garzik [this message]
2005-02-21 20:00 ` Linus Torvalds
2005-02-22 0:41 ` Pete Zaitcev
2005-02-22 1:48 ` Linus Torvalds
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=20050221183139.GA5020@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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®