linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Peter W. Morreale" <pmorreale@novell.com>
Cc: Christoph Hellwig <hch@lst.de>,
	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: Fri, 15 May 2009 11:35:55 +0200	[thread overview]
Message-ID: <20090515093554.GX4140@kernel.dk> (raw)
In-Reply-To: <1242225024.19182.174.camel@hermosa>

On Wed, May 13 2009, Peter W. Morreale wrote:
> On Wed, 2009-05-13 at 15:08 +0200, Jens Axboe wrote:
> > 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?
> > 
> 
> No, I didn't.  The rational was as explained in the commit log, merely
> that one size (eg: 2-8 threads) didn't fit all cases, so give the admin
> a chance at tuning w/o having to recompile.  

OK. In general I think it's a pretty bad idea to add such knobs before
there are specific use cases, as we have to maintain them forever. I
didn't track where this patch came from, I just spotted it in mainline
during the merge window.

> More importantly, I didn't know that Jens was working on significant
> changes to writeback.  This is sorely needed as from what I see in the
> code, writeback is very unfair to 'fast' block devices (when both 'fast'
> and 'slow' devices co-exist), and consequently, the apps that reference
> them.  
> 
> Jens: When do you expect to complete the per-bdi patchset?

Sooner rather than later. I've been working on it the past few days, I
needed to make some fundemental changes to support WB_SYNC_ALL and
sync(1) properly, unfortunately. I'll be posting an updated patchset
early next week.

> In any event, it is not a good idea to expose knobs that will soon be
> obviated so please pull the patch. 

Good, I have reverted the commit in my for-linus branch and will be
asking Linus to pull that soonish.

-- 
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>

      reply	other threads:[~2009-05-15  9:35 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
2009-05-13 14:30   ` Peter W. Morreale
2009-05-15  9:35     ` Jens Axboe [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=20090515093554.GX4140@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).