From: Padraig Brady <padraig.brady@corvil.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Love <rml@tech9.net>,
akpm@digeo.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: benchmarks of O_STREAMING in 2.5
Date: Mon, 21 Oct 2002 15:32:34 +0100 [thread overview]
Message-ID: <3DB41002.2050204@corvil.com> (raw)
In-Reply-To: 1035211132.27309.131.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
> On Thu, 2002-10-17 at 03:53, Robert Love wrote:
>
>>I gave the O_STREAMING in Andrew's 2.5-mm tree the treatment..
>>
>>Short summary: It works.
>>
>>The streaming read test in the following benchmarks is simply a read()
>>in 64KB byte chunks of an 800MB file.
>
> All you now need to do is make it work with an API thats usable by the
> other 99% of real world apps, is extensible and sensible ways and
> therefore can be used.
I'm confused. Isn't this just an O_STREAM flag on open/fcntl ?
How could it be simpler? I suppose the VM could do better than
it currently does automatically but there is no harm in the app
giving a hint like this thus allowing stuff to be dropped from
the cache more aggresively?
Pádraig.
next prev parent reply other threads:[~2002-10-21 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 2:53 benchmarks of O_STREAMING in 2.5 Robert Love
2002-10-17 7:33 ` Giuliano Pochini
2002-10-17 7:40 ` Robert Love
2002-10-21 14:38 ` Alan Cox
2002-10-21 14:32 ` Padraig Brady [this message]
2002-10-21 16:14 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-10-17 22:59 Dieter Nützel
[not found] <1034823201.722.429.camel@phantasy.suse.lists.linux.kernel>
[not found] ` <1035211132.27309.131.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2002-10-21 14:35 ` Andi Kleen
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=3DB41002.2050204@corvil.com \
--to=padraig.brady@corvil.com \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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.