From: Vivek Goyal <vgoyal@redhat.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: lsf-pc@lists.linux-foundation.org,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Dave Chinner <david@fromorbit.com>,
Wu Fengguang <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] [ATTEND] Future writeback topics
Date: Mon, 23 Jan 2012 15:19:04 -0500 [thread overview]
Message-ID: <20120123201904.GN25986@redhat.com> (raw)
In-Reply-To: <4F1C141C.2050704@panasas.com>
On Sun, Jan 22, 2012 at 03:50:20PM +0200, Boaz Harrosh wrote:
> Hi
>
> Now that we have the "IO-less dirty throttling" in and kicking (ass I might say)
> Are there plans for second stage? I can see few areas that need some love.
>
> [IO Fairness, time sorted writeback, properly delayed writeback]
>
> As we started to talk about in another thread: "[LSF/MM TOPIC] a few storage topics"
> I would like to propose the following topics:
>
> * Do we have enough information for the time of dirty of pages, such as the
> IO-elevators information, readily available to be used at the VFS layer.
Assuming it is available, what's the plan. How would VFS layer make use
of it?
Thanks
Vivek
prev parent reply other threads:[~2012-01-23 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 13:50 [LSF/MM TOPIC] [ATTEND] Future writeback topics Boaz Harrosh
2012-01-22 14:49 ` James Bottomley
2012-01-22 15:37 ` Boaz Harrosh
2012-01-22 15:49 ` [Lsf-pc] " James Bottomley
2012-01-22 22:11 ` Boaz Harrosh
2012-01-22 15:27 ` James Bottomley
2012-01-23 12:33 ` Johannes Weiner
2012-01-23 13:41 ` Boaz Harrosh
2012-01-23 18:15 ` Jan Kara
2012-01-23 20:19 ` Vivek Goyal [this message]
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=20120123201904.GN25986@redhat.com \
--to=vgoyal@redhat.com \
--cc=aarcange@redhat.com \
--cc=bharrosh@panasas.com \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).