From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Peter W Morreale <pmorreale@novell.com>,
torvalds@osdl.org, akpm@osdl.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: do we really want to export more pdflush details in sysctls
Date: Wed, 13 May 2009 15:08:11 +0200 [thread overview]
Message-ID: <20090513130811.GE4140@kernel.dk> (raw)
In-Reply-To: <20090513130128.GA10382@lst.de>
On Wed, May 13 2009, Christoph Hellwig wrote:
> Hi all,
>
> commit fafd688e4c0c34da0f3de909881117d374e4c7af titled
> "mm: add /proc controls for pdflush threads" adds two more sysctl
> variables exposing details about pdflush threads. At the same time
> Jens Axboe is working on the per-bdi writeback patchset which will
> hopefull soon get rid of the pdflush threads in their current form.
>
> Is it really a good idea to expose more details now or should we revert
> this patch before 2.6.30 is out?
Pained me as well when updating the patchset. I see little value in
these knobs as it is, I'm imagining that the submitter must have had a
use case where it made some difference?
--
Jens Axboe
--
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-05-13 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 13:01 do we really want to export more pdflush details in sysctls Christoph Hellwig
2009-05-13 13:08 ` Jens Axboe [this message]
2009-05-13 14:30 ` Peter W. Morreale
2009-05-15 9:35 ` Jens Axboe
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=20090513130811.GE4140@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pmorreale@novell.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).