All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Ben LaHaise <bcrl@redhat.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Martin Rauh <martin.rauh@gmx.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Writing on raw device with software RAID 0 is slow
Date: Thu, 1 Mar 2001 16:02:01 +0000	[thread overview]
Message-ID: <20010301160201.P26280@redhat.com> (raw)
In-Reply-To: <20010301121418.A7647@redhat.com> <Pine.LNX.4.30.0103011035520.13184-100000@today.toronto.redhat.com>
In-Reply-To: <Pine.LNX.4.30.0103011035520.13184-100000@today.toronto.redhat.com>; from bcrl@redhat.com on Thu, Mar 01, 2001 at 10:44:38AM -0500

Hi,

On Thu, Mar 01, 2001 at 10:44:38AM -0500, Ben LaHaise wrote:
> 
> On Thu, 1 Mar 2001, Stephen C. Tweedie wrote:
> 
> > Raw IO is always synchronous: it gets flushed to disk before the write
> > returns.  You don't get any write-behind with raw IO, so the smaller
> > the blocksize you write in, the slower things get.
> 
> More importantly, the mainstream raw io code only writes in 64KB chunks
> that are unpipelined, which can lead to writes not hitting the drive
> before the sector passes under the rw head.  You can work around this to
> some extent by issuing multiple writes (via threads, or the aio work I've
> done) at the expense of atomicity.  Also, before we allow locking of
> arbitrary larger ios in main memory, we need bean counting to prevent the
> obvious DoSes.

Yep.  There shouldn't be any problem increasing the 64KB size, it's
only the lack of accounting for the pinned memory which stopped me
increasing it by default.

--Stephen

  reply	other threads:[~2001-03-01 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28 14:58 Writing on raw device with software RAID 0 is slow Martin Rauh
2001-03-01 12:14 ` Stephen C. Tweedie
2001-03-01 15:44   ` Ben LaHaise
2001-03-01 16:02     ` Stephen C. Tweedie [this message]
2001-03-01 16:08       ` Ben LaHaise
2001-03-01 16:29         ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
2001-03-01 16:47 Douglas Gilbert

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=20010301160201.P26280@redhat.com \
    --to=sct@redhat.com \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.rauh@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.