From: Pete Zaitcev <zaitcev@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: Merging fails reading /dev/uba1
Date: Mon, 21 Feb 2005 16:41:51 -0800 [thread overview]
Message-ID: <20050221164151.0a63f906@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0502211152330.2378@ppc970.osdl.org>
On Mon, 21 Feb 2005 12:00:48 -0800 (PST), Linus Torvalds <torvalds@osdl.org> wrote:
> That said, I'm surprised that the difference in performance is _that_
> large. Regardless of whether the disk blocksize is 512 bytes or 4096
> bytes, you should be getting IO merging - it might use more CPU time, but
> the actual IO should still be done in much larger blocks.
I am surprised too. Jens says "ub effectively disables merging by setting
max hw/phys segment limit of 1." But surely this ought not to be a problem
for reads within the same page.
> int size = 4096;
> ioctl(fd, BLKBSZSET, &size);
Thank you for the tip. This works fine, 4KB I/O is restored for dd.
However, I still have this problem with people who use ub to read CF sticks
from their cameras, mounted as FAT or VFAT. I verified that the effect of
this ioctl disappears at mount time, just as you said.
I'll think what I can do about it.
-- Pete
next prev parent reply other threads:[~2005-02-22 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 4:00 Merging fails reading /dev/uba1 Pete Zaitcev
2005-02-21 7:51 ` Jens Axboe
2005-02-21 18:24 ` Pete Zaitcev
2005-02-21 18:31 ` Jeff Garzik
2005-02-21 20:00 ` Linus Torvalds
2005-02-22 0:41 ` Pete Zaitcev [this message]
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=20050221164151.0a63f906@localhost.localdomain \
--to=zaitcev@redhat.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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