From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dave Chinner <david@fromorbit.com>,
Zheng Liu <gnehzuil.liu@gmail.com>
Subject: Re: [v2] fadvise: perform WILLNEED readahead asynchronously
Date: Thu, 10 Jan 2013 10:35:39 +0100 [thread overview]
Message-ID: <50EE8B6B.1050204@gmail.com> (raw)
In-Reply-To: <20121225022251.GA25992@dcvr.yhbt.net>
Hello,
Il 25/12/2012 03:22, Eric Wong ha scritto:
> Any other (Free Software) applications that might benefit from
> lower FADV_WILLNEED latency?
Not with fadvise but with madvise. Libreoffice / Openoffice.org have
this comment:
// On Linux, madvise(..., MADV_WILLNEED) appears to have the undesirable
// effect of not returning until the data has actually been paged in, so
// that its net effect would typically be to slow down the process
// (which could start processing at the beginning of the data while the
// OS simultaneously pages in the rest); on other platforms, it remains
// to be evaluated whether madvise or equivalent is available and
// actually useful:
See:
http://cgit.freedesktop.org/libreoffice/core/tree/sal/osl/unx/file.cxx#n1213
May the same approach be extended to madvise MADV_WILLNEED?
thanks,
riccardo magliocchetti
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-10 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 2:22 [PATCH v2] fadvise: perform WILLNEED readahead asynchronously Eric Wong
2012-12-27 7:01 ` Zheng Liu
2013-01-05 11:46 ` Simon Jeons
2013-01-10 4:05 ` Eric Wong
2013-01-10 9:35 ` Riccardo Magliocchetti [this message]
2013-01-10 11:14 ` [v2] " Eric Wong
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=50EE8B6B.1050204@gmail.com \
--to=riccardo.magliocchetti@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=david@fromorbit.com \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=normalperson@yhbt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).