From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, peterz@infradead.org, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
npiggin@suse.de
Subject: Re: Increase dirty_ratio and dirty_background_ratio?
Date: Thu, 08 Jan 2009 11:55:01 -0500 [thread overview]
Message-ID: <1231433701.14304.24.camel@think.oraclecorp.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0901080842180.3283@localhost.localdomain>
On Thu, 2009-01-08 at 08:48 -0800, Linus Torvalds wrote:
>
> On Thu, 8 Jan 2009, David Miller wrote:
>
> > From: Andrew Morton <akpm@linux-foundation.org>
> > Date: Thu, 8 Jan 2009 03:02:45 -0800
> >
> > > The kernel can't get this right - it doesn't know the usage
> > > patterns/workloads, etc.
> >
> > I don't agree with that.
>
> We can certainly try to tune it better.
>
Does it make sense to hook into kupdate? If kupdate finds it can't meet
the no-data-older-than 30 seconds target, it lowers the sync/async combo
down to some reasonable bottom.
If it finds it is going to sleep without missing the target, raise the
combo up to some reasonable top.
-chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, peterz@infradead.org, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
npiggin@suse.de
Subject: Re: Increase dirty_ratio and dirty_background_ratio?
Date: Thu, 08 Jan 2009 11:55:01 -0500 [thread overview]
Message-ID: <1231433701.14304.24.camel@think.oraclecorp.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0901080842180.3283@localhost.localdomain>
On Thu, 2009-01-08 at 08:48 -0800, Linus Torvalds wrote:
>
> On Thu, 8 Jan 2009, David Miller wrote:
>
> > From: Andrew Morton <akpm@linux-foundation.org>
> > Date: Thu, 8 Jan 2009 03:02:45 -0800
> >
> > > The kernel can't get this right - it doesn't know the usage
> > > patterns/workloads, etc.
> >
> > I don't agree with that.
>
> We can certainly try to tune it better.
>
Does it make sense to hook into kupdate? If kupdate finds it can't meet
the no-data-older-than 30 seconds target, it lowers the sync/async combo
down to some reasonable bottom.
If it finds it is going to sleep without missing the target, raise the
combo up to some reasonable top.
-chris
--
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:[~2009-01-08 16:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 15:45 Increase dirty_ratio and dirty_background_ratio? Jan Kara
2009-01-07 16:25 ` Peter Zijlstra
2009-01-07 16:25 ` Peter Zijlstra
2009-01-07 16:39 ` Linus Torvalds
2009-01-07 16:39 ` Linus Torvalds
2009-01-07 20:51 ` David Miller
2009-01-07 20:51 ` David Miller
2009-01-08 11:02 ` Andrew Morton
2009-01-08 11:02 ` Andrew Morton
2009-01-08 16:24 ` David Miller
2009-01-08 16:24 ` David Miller
2009-01-08 16:48 ` Linus Torvalds
2009-01-08 16:48 ` Linus Torvalds
2009-01-08 16:55 ` Chris Mason [this message]
2009-01-08 16:55 ` Chris Mason
2009-01-08 17:05 ` Linus Torvalds
2009-01-08 17:05 ` Linus Torvalds
2009-01-08 19:57 ` Jan Kara
2009-01-08 19:57 ` Jan Kara
2009-01-08 20:01 ` David Miller
2009-01-08 20:01 ` David Miller
2009-01-09 18:02 ` Jan Kara
2009-01-09 19:00 ` Andrew Morton
2009-01-09 19:00 ` Andrew Morton
2009-01-09 19:07 ` Chris Mason
2009-01-09 19:07 ` Chris Mason
2009-01-09 22:31 ` david
2009-01-09 21:34 ` Peter Zijlstra
2009-01-09 21:34 ` Peter Zijlstra
2009-01-14 3:29 ` Nick Piggin
2009-01-14 3:29 ` Nick Piggin
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=1231433701.14304.24.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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 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.