From: Arjan van de Ven <arjan@infradead.org>
To: Manish Regmi <regmi.manish@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Linux disk performance.
Date: Mon, 18 Dec 2006 09:35:39 +0100 [thread overview]
Message-ID: <1166431020.3365.931.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <652016d30612172007m58d7a828q378863121ebdc535@mail.gmail.com>
>
> Can we achieve smooth write times in Linux?
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.
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2006-12-18 11:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 4:07 Manish Regmi
2006-12-18 8:35 ` Arjan van de Ven [this message]
2006-12-18 12:39 ` Manish Regmi
2006-12-18 12:54 ` Nick Piggin
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=1166431020.3365.931.camel@laptopd505.fenrus.org \
--to=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
all inboxes | Powered by JetHome®