From: Peter Zijlstra <peterz@infradead.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 12/12] bdi: use bdi_stat_sum() for more accurate debugfs stats
Date: Thu, 19 Nov 2009 09:12:04 +0100 [thread overview]
Message-ID: <1258618324.3931.35.camel@laptop> (raw)
In-Reply-To: <20091119075944.GA5922@localhost>
On Thu, 2009-11-19 at 15:59 +0800, Wu Fengguang wrote:
> On Wed, Nov 18, 2009 at 06:38:49PM +0800, Peter Zijlstra wrote:
> > On Wed, 2009-11-18 at 16:27 +0800, Wu Fengguang wrote:
> > > plain text document attachment (bdi-debug-dump-sum.patch)
> > > CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> > > ---
> > > mm/backing-dev.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > --- linux.orig/mm/backing-dev.c 2009-11-18 16:25:28.000000000 +0800
> > > +++ linux/mm/backing-dev.c 2009-11-18 16:26:10.000000000 +0800
> > > @@ -104,8 +104,8 @@ static int bdi_debug_stats_show(struct s
> > > "wb_mask: %8lx\n"
> > > "wb_list: %8u\n"
> > > "wb_cnt: %8u\n",
> > > - (unsigned long) K(bdi_stat(bdi, BDI_WRITEBACK)),
> > > - (unsigned long) K(bdi_stat(bdi, BDI_RECLAIMABLE)),
> > > + (unsigned long) K(bdi_stat_sum(bdi, BDI_WRITEBACK)),
> > > + (unsigned long) K(bdi_stat_sum(bdi, BDI_RECLAIMABLE)),
> > > K(bdi_thresh), K(dirty_thresh),
> > > K(background_thresh), nr_wb, nr_dirty, nr_io, nr_more_io,
> > > !list_empty(&bdi->bdi_list), bdi->state, bdi->wb_mask,
> > >
> >
> > Is this really important? This patch is basically a local DoS for large
> > machines.
>
> I did this patch after seeing inaccurate exported numbers,
> it may be confusing..
>
> > Imagine someone doing:
> >
> > while :; do cat /debug/bdi/*/stats; done
> >
> > on a 512 cpu box.
>
> Yes there will be overheads. However it's always possible to
> create local DoS with some other kind of busy loop?
Preferably not of the kind that renders your box unusable, esp by unpriv
users.
But yes there are probably a few local DoS' around, but I don't think
that warrants adding another one.
next prev parent reply other threads:[~2009-11-19 8:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091118082648.140755818@intel.com>
[not found] ` <20091118082846.170413359@intel.com>
2009-11-18 9:59 ` [PATCH 06/12] writeback: remove unused nonblocking and congestion checks (gfs2) Steven Whitehouse
2009-11-18 10:09 ` Wu Fengguang
2009-11-18 11:13 ` Steven Whitehouse
[not found] ` <20091118082846.921451469@intel.com>
2009-11-18 10:38 ` [PATCH 12/12] bdi: use bdi_stat_sum() for more accurate debugfs stats Peter Zijlstra
2009-11-19 7:59 ` Wu Fengguang
2009-11-19 8:12 ` Peter Zijlstra [this message]
2009-11-19 8:17 ` Wu Fengguang
[not found] ` <20091118082846.279046849@intel.com>
2009-11-18 21:27 ` [PATCH 07/12] writeback: remove unused nonblocking and congestion checks (xfs) Dave Chinner
2009-11-19 8:05 ` Wu Fengguang
2009-11-20 7:24 ` Dave Chinner
[not found] ` <20091118082845.828021716@intel.com>
2009-11-19 8:11 ` [PATCH 03/12] writeback: remove unused nonblocking and congestion checks (pohmelfs) Wu Fengguang
2009-11-19 11:04 ` Evgeniy Polyakov
2009-11-20 1:53 ` Wu Fengguang
2009-11-21 11:23 ` Evgeniy Polyakov
[not found] ` <20091118082845.936295466@intel.com>
2009-11-19 8:09 ` [PATCH 04/12] writeback: remove unused nonblocking and congestion checks (afs) Wu Fengguang
2009-11-19 16:51 ` David Howells
[not found] ` <20091118082846.404788666@intel.com>
2009-11-24 16:18 ` [PATCH 08/12] ext4: remove encountered_congestion trace tytso
[not found] ` <20091118082846.530386547@intel.com>
2009-11-24 16:18 ` [PATCH 09/12] ext4: remove unused parameter wbc from __ext4_journalled_writepage() tytso
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=1258618324.3931.35.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.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).