From: Jan Kara <jack@suse.cz>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v3 16/18] ext4: update ext4_ext_remove_space trace point
Date: Fri, 19 Apr 2013 07:16:15 +0200 [thread overview]
Message-ID: <20130419051615.GG19244@quack.suse.cz> (raw)
In-Reply-To: <1365498867-27782-17-git-send-email-lczerner@redhat.com>
On Tue 09-04-13 11:14:25, Lukas Czerner wrote:
> Add "end" variable.
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext4/extents.c | 6 +++---
> include/trace/events/ext4.h | 21 ++++++++++++++-------
> 2 files changed, 17 insertions(+), 10 deletions(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 4adaa8a..9023b76 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -2666,7 +2666,7 @@ int ext4_ext_remove_space(struct inode *inode, ext4_lblk_t start,
> return PTR_ERR(handle);
>
> again:
> - trace_ext4_ext_remove_space(inode, start, depth);
> + trace_ext4_ext_remove_space(inode, start, end, depth);
>
> /*
> * Check if we are removing extents inside the extent tree. If that
> @@ -2832,8 +2832,8 @@ again:
> }
> }
>
> - trace_ext4_ext_remove_space_done(inode, start, depth, partial_cluster,
> - path->p_hdr->eh_entries);
> + trace_ext4_ext_remove_space_done(inode, start, end, depth,
> + partial_cluster, path->p_hdr->eh_entries);
>
> /* If we still have something in the partial cluster and we have removed
> * even the first extent, then we should free the blocks in the partial
> diff --git a/include/trace/events/ext4.h b/include/trace/events/ext4.h
> index 60b329a..c92500c 100644
> --- a/include/trace/events/ext4.h
> +++ b/include/trace/events/ext4.h
> @@ -2027,14 +2027,16 @@ TRACE_EVENT(ext4_ext_rm_idx,
> );
>
> TRACE_EVENT(ext4_ext_remove_space,
> - TP_PROTO(struct inode *inode, ext4_lblk_t start, int depth),
> + TP_PROTO(struct inode *inode, ext4_lblk_t start,
> + ext4_lblk_t end, int depth),
>
> - TP_ARGS(inode, start, depth),
> + TP_ARGS(inode, start, end, depth),
>
> TP_STRUCT__entry(
> __field( dev_t, dev )
> __field( ino_t, ino )
> __field( ext4_lblk_t, start )
> + __field( ext4_lblk_t, end )
> __field( int, depth )
> ),
>
> @@ -2042,26 +2044,29 @@ TRACE_EVENT(ext4_ext_remove_space,
> __entry->dev = inode->i_sb->s_dev;
> __entry->ino = inode->i_ino;
> __entry->start = start;
> + __entry->end = end;
> __entry->depth = depth;
> ),
>
> - TP_printk("dev %d,%d ino %lu since %u depth %d",
> + TP_printk("dev %d,%d ino %lu start %u end %u depth %d",
> MAJOR(__entry->dev), MINOR(__entry->dev),
> (unsigned long) __entry->ino,
> (unsigned) __entry->start,
> + (unsigned) __entry->end,
> __entry->depth)
> );
>
> TRACE_EVENT(ext4_ext_remove_space_done,
> - TP_PROTO(struct inode *inode, ext4_lblk_t start, int depth,
> - ext4_lblk_t partial, unsigned short eh_entries),
> + TP_PROTO(struct inode *inode, ext4_lblk_t start, ext4_lblk_t end,
> + int depth, ext4_lblk_t partial, unsigned short eh_entries),
>
> - TP_ARGS(inode, start, depth, partial, eh_entries),
> + TP_ARGS(inode, start, end, depth, partial, eh_entries),
>
> TP_STRUCT__entry(
> __field( dev_t, dev )
> __field( ino_t, ino )
> __field( ext4_lblk_t, start )
> + __field( ext4_lblk_t, end )
> __field( int, depth )
> __field( ext4_lblk_t, partial )
> __field( unsigned short, eh_entries )
> @@ -2071,16 +2076,18 @@ TRACE_EVENT(ext4_ext_remove_space_done,
> __entry->dev = inode->i_sb->s_dev;
> __entry->ino = inode->i_ino;
> __entry->start = start;
> + __entry->end = end;
> __entry->depth = depth;
> __entry->partial = partial;
> __entry->eh_entries = eh_entries;
> ),
>
> - TP_printk("dev %d,%d ino %lu since %u depth %d partial %u "
> + TP_printk("dev %d,%d ino %lu start %u end %u depth %d partial %u "
> "remaining_entries %u",
> MAJOR(__entry->dev), MINOR(__entry->dev),
> (unsigned long) __entry->ino,
> (unsigned) __entry->start,
> + (unsigned) __entry->end,
> __entry->depth,
> (unsigned) __entry->partial,
> (unsigned short) __entry->eh_entries)
> --
> 1.7.7.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
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:[~2013-04-19 5:16 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 9:14 [PATCH v3 00/18] change invalidatepage prototype to accept length Lukas Czerner
2013-04-09 9:14 ` [PATCH v3 01/18] mm: " Lukas Czerner
2013-04-09 9:14 ` [PATCH v3 02/18] jbd2: change jbd2_journal_invalidatepage " Lukas Czerner
2013-04-09 13:22 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 03/18] ext4: use ->invalidatepage() length argument Lukas Czerner
2013-04-09 13:24 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 04/18] jbd: change journal_invalidatepage() to accept length Lukas Czerner
2013-04-09 13:20 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 05/18] xfs: use ->invalidatepage() length argument Lukas Czerner
2013-04-23 14:14 ` Theodore Ts'o
2013-04-23 21:06 ` Ben Myers
2013-04-09 9:14 ` [PATCH v3 06/18] ocfs2: " Lukas Czerner
2013-04-09 13:26 ` Jan Kara
2013-04-23 14:16 ` Theodore Ts'o
2013-05-02 22:00 ` Joel Becker
2013-04-09 9:14 ` [PATCH v3 07/18] ceph: " Lukas Czerner
2013-04-23 14:14 ` Theodore Ts'o
2013-04-23 16:04 ` Sage Weil
2013-04-09 9:14 ` [PATCH v3 08/18] gfs2: " Lukas Czerner
2013-04-09 9:29 ` [Cluster-devel] " Steven Whitehouse
2013-04-09 13:09 ` Bob Peterson
2013-04-09 13:27 ` Lukáš Czerner
2013-04-23 14:16 ` Theodore Ts'o
2013-04-23 14:17 ` Theodore Ts'o
2013-04-09 9:14 ` [PATCH v3 09/18] reiserfs: " Lukas Czerner
2013-04-09 13:27 ` Jan Kara
2013-04-10 9:51 ` Lukáš Czerner
2013-04-09 9:14 ` [PATCH v3 10/18] mm: teach truncate_inode_pages_range() to handle non page aligned ranges Lukas Czerner
2013-04-11 21:18 ` Jan Kara
2013-04-11 22:40 ` Hugh Dickins
2013-04-09 9:14 ` [PATCH v3 11/18] Revert "ext4: remove no longer used functions in inode.c" Lukas Czerner
2013-04-18 22:08 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 12/18] Revert "ext4: fix fsx truncate failure" Lukas Czerner
2013-04-18 22:21 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 13/18] ext4: use ext4_zero_partial_blocks in punch_hole Lukas Czerner
2013-04-19 5:03 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 14/18] ext4: remove unused discard_partial_page_buffers Lukas Czerner
2013-04-19 5:04 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 15/18] ext4: remove unused code from ext4_remove_blocks() Lukas Czerner
2013-04-19 5:15 ` Jan Kara
2013-04-09 9:14 ` [PATCH v3 16/18] ext4: update ext4_ext_remove_space trace point Lukas Czerner
2013-04-19 5:16 ` Jan Kara [this message]
2013-04-09 9:14 ` [PATCH v3 17/18] ext4: make punch hole code path work with bigalloc Lukas Czerner
2013-04-20 13:42 ` Jan Kara
2013-04-23 9:19 ` Zheng Liu
2013-04-24 11:08 ` Lukáš Czerner
2013-04-24 11:29 ` Zheng Liu
2013-04-24 10:57 ` Lukáš Czerner
2013-04-09 9:14 ` [PATCH v3 18/18] ext4: Allow punch hole with bigalloc enabled Lukas Czerner
2013-04-20 13:43 ` Jan Kara
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=20130419051615.GG19244@quack.suse.cz \
--to=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).