All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: 'Shuoran' <liushuoran@huawei.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] Introduce lifetime write IO statistics
Date: Wed, 27 Jan 2016 21:03:14 +0800	[thread overview]
Message-ID: <56A8C012.7030904@kernel.org> (raw)
In-Reply-To: <00da01d158e9$f170a290$d451e7b0$@samsung.com>

On 1/27/16 6:02 PM, Chao Yu wrote:
> IMO, maybe it's better to use journal log in data segments to store

data -> node

> checkpoint related data, maybe more nats/sits entries.
> 
> And another thing is I'm in doubt that whether it is enough to use cp +
> data journal to update stat, since abnormal pow-cut after a normal cp would

ditto.

> make us losing all stats saved before.

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

  reply	other threads:[~2016-01-27 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  7:40 [PATCH] Introduce lifetime write IO statistics Liu Shuoran
2016-01-26  9:24 ` Chao Yu
2016-01-26 10:12   ` Shuoran
2016-01-27  7:20     ` Chao Yu
2016-01-27  7:40       ` Shuoran
2016-01-27 10:02         ` Chao Yu
2016-01-27 13:03           ` Chao Yu [this message]
2016-01-27 22:26           ` Jaegeuk Kim
2016-01-28  1:20             ` Chao Yu

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=56A8C012.7030904@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=liushuoran@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.