From: Eric Wong <normalperson@yhbt.net>
To: Simon Jeons <simon.jeons@gmail.com>
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: [PATCH v2] fadvise: perform WILLNEED readahead asynchronously
Date: Thu, 10 Jan 2013 04:05:46 +0000 [thread overview]
Message-ID: <20130110040546.GA23797@dcvr.yhbt.net> (raw)
In-Reply-To: <1357386394.9001.0.camel@kernel.cn.ibm.com>
Simon Jeons <simon.jeons@gmail.com> wrote:
> On Tue, 2012-12-25 at 02:22 +0000, Eric Wong wrote:
>
> Please add changelog.
Changes since v1:
* separate unbound workqueue for high-priority tasks
* account for inflight readahead to avoid denial-of-service
* limit concurrency for non-high-priority tasks (1 per CPU, same as aio)
* take IO priority of requesting process into account when in workqueue.
* process queued readahead in 2M chunks to help ensure fairness between
multiple requests with few CPUs/workqueues. Idle tasks get smaller
256K chunks.
* stops readahead for idle tasks on read congestion
Will try to benchmark with Postgres when I get the chance.
Any other (Free Software) applications that might benefit from
lower FADV_WILLNEED latency?
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Eric Wong <normalperson@yhbt.net>
To: Simon Jeons <simon.jeons@gmail.com>
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: [PATCH v2] fadvise: perform WILLNEED readahead asynchronously
Date: Thu, 10 Jan 2013 04:05:46 +0000 [thread overview]
Message-ID: <20130110040546.GA23797@dcvr.yhbt.net> (raw)
In-Reply-To: <1357386394.9001.0.camel@kernel.cn.ibm.com>
Simon Jeons <simon.jeons@gmail.com> wrote:
> On Tue, 2012-12-25 at 02:22 +0000, Eric Wong wrote:
>
> Please add changelog.
Changes since v1:
* separate unbound workqueue for high-priority tasks
* account for inflight readahead to avoid denial-of-service
* limit concurrency for non-high-priority tasks (1 per CPU, same as aio)
* take IO priority of requesting process into account when in workqueue.
* process queued readahead in 2M chunks to help ensure fairness between
multiple requests with few CPUs/workqueues. Idle tasks get smaller
256K chunks.
* stops readahead for idle tasks on read congestion
Will try to benchmark with Postgres when I get the chance.
Any other (Free Software) applications that might benefit from
lower FADV_WILLNEED latency?
next prev parent reply other threads:[~2013-01-10 4:05 UTC|newest]
Thread overview: 12+ 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-25 2:22 ` Eric Wong
2012-12-27 7:01 ` Zheng Liu
2012-12-27 7:01 ` Zheng Liu
2013-01-05 11:46 ` Simon Jeons
2013-01-05 11:46 ` Simon Jeons
2013-01-10 4:05 ` Eric Wong [this message]
2013-01-10 4:05 ` Eric Wong
2013-01-10 9:35 ` [v2] " Riccardo Magliocchetti
2013-01-10 9:35 ` Riccardo Magliocchetti
2013-01-10 11:14 ` Eric Wong
2013-01-10 11:14 ` 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=20130110040546.GA23797@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--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=simon.jeons@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 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.