public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Manish Regmi <regmi.manish@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Linux disk performance.
Date: Mon, 18 Dec 2006 23:54:21 +1100	[thread overview]
Message-ID: <45868F7D.4020400@yahoo.com.au> (raw)
In-Reply-To: <652016d30612180439y6cd12089l115e4ef6ce2e59fe@mail.gmail.com>

Manish Regmi wrote:
> On 12/18/06, Arjan van de Ven <arjan@infradead.org> wrote:
> 
>> if you want truely really smooth writes you'll have to work for it,
>> since "bumpy" writes tend to be better for performance so naturally the
>> kernel will favor those.
>>
>> to get smooth writes you'll need to do a threaded setup where you do an
>> msync/fdatasync/sync_file_range on a frequent-but-regular interval from
>> a thread. Be aware that this is quite likely to give you lower maximum
>> performance than the batching behavior though.
>>
> 
> Thanks...
> 
> But isn't O_DIRECT supposed to bypass buffering in Kernel?
> Doesn't it directly write to disk?
> I tried to put fdatasync() at regular intervals but there was no
> visible effect.
> 

I don't know exactly how to interpret the numbers you gave, but
they look like they might be a (HZ quantised) delay coming from
block layer plugging.

O_DIRECT bypasses caching, but not (all) buffering.

Not sure whether the block layer can handle an unplug_delay set
to 0, but that might be something to try (see block/ll_rw_blk.c).

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-12-18 13:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18  4:07 Linux disk performance Manish Regmi
2006-12-18  8:35 ` Arjan van de Ven
2006-12-18 12:39   ` Manish Regmi
2006-12-18 12:54     ` Nick Piggin [this message]
2006-12-18 13:07     ` Erik Mouw
2006-12-19  6:22       ` Manish Regmi
2006-12-19  6:38         ` Nick Piggin
2006-12-19 12:18           ` Arjan van de Ven
2006-12-20 11:17           ` Manish Regmi
2006-12-22  0:14             ` Bhanu Kalyan Chetlapalli
2006-12-22  5:30               ` Manish Regmi
2006-12-22  5:39                 ` Bhanu Kalyan Chetlapalli
2006-12-22  5:56                   ` Manish Regmi
2006-12-20 22:29     ` Bill Davidsen
2006-12-21  6:03       ` Manish Regmi
2006-12-21  7:15         ` Daniel Cheng
2006-12-21 13:22         ` Erik Mouw
2006-12-22  5:39           ` Manish Regmi
2006-12-27 15:50       ` Phillip Susi
2007-01-01  1:59         ` Bill Davidsen

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=45868F7D.4020400@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=arjan@infradead.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regmi.manish@gmail.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