linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Curt Wohlgemuth <curtw@google.com>
To: Jan Kara <jack@suse.cz>
Cc: lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] Writeback - current state and future
Date: Fri, 4 Feb 2011 10:06:45 -0800	[thread overview]
Message-ID: <AANLkTikUwWOrz_LF1nO=y9cE=Ndt_CUMH-HwH244z6n0@mail.gmail.com> (raw)
In-Reply-To: <20110204164222.GG4104@quack.suse.cz>

I think it would also be valuable to include a discussion of writeback
testing, so perhaps we can go beyond simply large numbers of dd
processes.

On Fri, Feb 4, 2011 at 8:42 AM, Jan Kara <jack@suse.cz> wrote:
>  Hi,
>
>  I'd like to have one session about writeback. The content would highly
> depend on the current state of things but on a general level, I'd like to
> quickly sum up what went into the kernel (or is mostly ready to go) since
> last LSF (handling of background writeback, livelock avoidance), what is
> being worked on - IO-less balance_dirty_pages() (if it won't be in the
> mostly done section), what other things need to be improved (kswapd
> writeout, writeback_inodes_sb_if_idle() mess, come to my mind now)
>
>                                                                Honza
> --
> Jan Kara <jack@suse.cz>
> SUSE Labs, CR
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-02-04 18:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 16:42 Jan Kara
2011-02-04 18:06 ` Curt Wohlgemuth [this message]
2011-02-05  7:55   ` Tao Ma
2011-02-06 10:43 ` Boaz Harrosh
2011-02-06 15:13   ` Sorin Faibish
2011-02-06 16:24     ` Boaz Harrosh
2011-02-11 14:47     ` Jan Kara
2011-02-11 16:22       ` sfaibish
2011-02-26 21:03         ` Sorin Faibish
2011-02-26 21:07           ` [Lsf-pc] " James Bottomley
2011-02-26 23:21             ` Sorin Faibish
2011-02-26 23:48               ` James Bottomley
2011-02-27  1:50                 ` Trond Myklebust

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='AANLkTikUwWOrz_LF1nO=y9cE=Ndt_CUMH-HwH244z6n0@mail.gmail.com' \
    --to=curtw@google.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linuxfoundation.org \
    /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