All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Ameya Mitragotri <ameya.mitragotri@gmail.com>
Cc: linux-kernel@vger.kernel.org, suparna@in.ibm.com, pbadari@gmail.com
Subject: Re: fadvise+sync_file_range Vs O_DIRECT
Date: Tue, 03 Apr 2007 15:19:33 -0400	[thread overview]
Message-ID: <4612A8C5.1080103@cfl.rr.com> (raw)
In-Reply-To: <88df6dda0704030351u44fab6bcj20f9b48d24de861a@mail.gmail.com>

Ameya Mitragotri wrote:
> Hello,
> I am doing some benchmarking on writes to the hdd from a simple
> application (attached).
> Im benchmarking the writes using the following
> - write with O_DIRECT
> - write with fadvise + O_SYNC
> - write with fadvise + sync_file_range

Did you use overlapped aio with O_DIRECT or just send down one request 
at a time?


  reply	other threads:[~2007-04-03 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 10:51 fadvise+sync_file_range Vs O_DIRECT Ameya Mitragotri
2007-04-03 19:19 ` Phillip Susi [this message]
2007-04-04 10:42   ` Ameya Mitragotri
2007-04-04 14:24     ` Phillip Susi

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=4612A8C5.1080103@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=ameya.mitragotri@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@gmail.com \
    --cc=suparna@in.ibm.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 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.