From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 2/3] writeback: Add tracing to balance_dirty_pages Date: Mon, 21 Jun 2010 04:12:30 -0400 Message-ID: <20100621081230.GB19290@infradead.org> References: <1277083526-21002-1-git-send-email-david@fromorbit.com> <1277083526-21002-3-git-send-email-david@fromorbit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: axboe@kernel.dk, linux-fsdevel@vger.kernel.org To: Dave Chinner Return-path: Received: from [18.85.46.34] ([18.85.46.34]:33004 "EHLO bombadil.infradead.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1756431Ab0FUIMb (ORCPT ); Mon, 21 Jun 2010 04:12:31 -0400 Content-Disposition: inline In-Reply-To: <1277083526-21002-3-git-send-email-david@fromorbit.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > +/* pass flags explicitly */ which flags? > + TP_fast_assign( > + char *__name = "(none)"; > + > + __entry->wbc = (unsigned long)wbc & 0xffff; The wbc generally is allocated on stack, does it reall make sense to keep this? > + if (wbc->bdi) > + strncpy(__entry->name, dev_name(wbc->bdi->dev), 16); > + else > + strncpy(__entry->name, __name, 16); > + __entry->sb = !!wbc->sb; The bdi and sb fields are now gone from the writeback_control. But I think passing the bdi explicitly for the device name makes sense here.