Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: chao@kernel.org (Chao Yu)
Subject: [PATCH 11/11] erofs: support tracepoint
Date: Tue, 3 Jul 2018 21:52:13 +0800	[thread overview]
Message-ID: <080d2c39-83ee-9643-4ec6-0991ae31769c@kernel.org> (raw)
In-Reply-To: <ad8b5812-699e-9c99-3d76-02fa65635c6c@huawei.com>

Hi Xiang,

On 2018/7/3 17:44, Gao Xiang wrote:
> Hi Chao,
> 
> On 2018/6/22 10:01, Chao Yu wrote:
>> Add tracepoints for ->readpage{,s}, ->lookup.
>>
>> Signed-off-by: Chao Yu <yuchao0 at huawei.com> ---
> 
> Very useful feature (I could use it for the new unzip implementation :) )

It seems we need more tracepoints for debug or accounting, but now I just add
basic ones, let's add more. ;)

> 
>>  fs/erofs/data.c              |   8 +++
>>  fs/erofs/namei.c             |   5 ++
>>  fs/erofs/super.c             |   2 +
>>  fs/erofs/unzip.c             |  10 +++-
>>  include/trace/events/erofs.h | 109 +++++++++++++++++++++++++++++++++++
>>  5 files changed, 133 insertions(+), 1 deletion(-)
>>  create mode 100644 include/trace/events/erofs.h
>>
>> +	trace_erofs_readpage(page, true);
>> +
>>  	bio = erofs_read_raw_page(NULL, page->mapping,
>>  		page, &last_block, 1, false);
>>  
>> @@ -354,6 +359,9 @@ static int erofs_raw_access_readpages(struct file *filp,
>>  	erofs_off_t last_block;
>>  	struct bio *bio = NULL;
>>  	gfp_t gfp = readahead_gfp_mask(mapping);
>> +	struct page *page = list_last_entry(pages, struct page, lru);
>> +
>> +	trace_erofs_readpages(mapping->host, page, nr_pages, true);
>>  
>>  	for (; nr_pages; --nr_pages) {
>>  		struct page *page = list_entry(pages->prev, struct page, lru);
> 
> minor, how about remove the in-loop 'page' defination?

Okay, let me remove this.

Thanks,

> 
> Reviewed-by: Gao Xiang <gaoxiang25 at huawei.com>
> 
> Thanks,
> Gao Xiang
> 
>> diff --git a/fs/erofs/namei.c b/fs/erofs/namei.c
>> index e30294b279d1..b701d9ba52a6 100644
>> --- a/fs/erofs/namei.c
>> +++ b/fs/erofs/namei.c

  reply	other threads:[~2018-07-03 13:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  2:01 [PATCH 01/11] erofs: fix compile error Chao Yu
2018-06-22  2:01 ` [PATCH 02/11] erofs: fix to avoid potential overflow Chao Yu
2018-06-22  2:01 ` [PATCH 03/11] erofs: fix missing endian conversion Chao Yu
2018-06-22  2:01 ` [PATCH 04/11] erofs: fix to do endian conversion correctly Chao Yu
2018-06-22  2:01 ` [PATCH 05/11] erofs: fix to handle return value of erofs_init_page_bundle() correctly Chao Yu
2018-06-22  2:01 ` [PATCH 06/11] erofs: fix to return correct value of alloc_inode Chao Yu
2018-06-22  2:01 ` [PATCH 07/11] erofs: remove unused EROFS_XATTR_INDEX_ADVISE Chao Yu
2018-06-22  2:01 ` [PATCH 08/11] erofs: support special inode Chao Yu
2018-07-03  5:31   ` Gao Xiang
2018-07-03 13:48     ` Chao Yu
2018-08-01  8:17       ` Gao Xiang
2018-08-01  8:40         ` 答复: " liguifu (C)
2018-06-22  2:01 ` [PATCH 09/11] erofs: introduce parse_options() Chao Yu
2018-06-22  2:01 ` [PATCH 10/11] erofs: introduce error injection infrastructure Chao Yu
2018-06-30 15:44   ` [PATCH v4] " Gao Xiang
2018-06-30 18:39   ` [PATCH v5] " Gao Xiang
2018-07-01  3:56     ` Chao Yu
2018-07-01  4:04       ` Gao Xiang
2018-06-22  2:01 ` [PATCH 11/11] erofs: support tracepoint Chao Yu
2018-07-03  9:44   ` Gao Xiang
2018-07-03 13:52     ` Chao Yu [this message]
2018-07-03 14:22       ` Gao Xiang

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=080d2c39-83ee-9643-4ec6-0991ae31769c@kernel.org \
    --to=chao@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