public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerome Marchand <jmarchan@redhat.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Nitin Gupta <ngupta@vflare.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 4/4] zram: report failed read and writes stats
Date: Thu, 16 Jan 2014 10:45:35 +0100	[thread overview]
Message-ID: <52D7AA3F.2030501@redhat.com> (raw)
In-Reply-To: <20140116005844.GN1992@bbox>

On 01/16/2014 01:58 AM, Minchan Kim wrote:
> On Wed, Jan 15, 2014 at 01:16:17PM +0300, Sergey Senozhatsky wrote:
>> zram accounted but did not report numbers of failed read
>> and write queries. make these stats available as failed_reads
>> and failed_writes attrs.
>>
>> Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Acked-by: Minchan Kim <minchan@kernel.org>
> 

This of course depends on third patch, but since I have no objection
to the ZRAM_ATTR_RO() macro part:

Acked-by: Jerome Marchand <jmarchan@redhat.com>


      reply	other threads:[~2014-01-16  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 10:16 [PATCHv2 0/4] zram stats rework and code cleanup Sergey Senozhatsky
2014-01-15 10:16 ` [PATCHv2 1/4] zram: drop `init_done' struct zram member Sergey Senozhatsky
2014-01-15 10:16 ` [PATCHv2 2/4] zram: do not pass rw argument to __zram_make_request() Sergey Senozhatsky
2014-01-15 10:16 ` [PATCHv2 3/4] zram: rework reported to end-user zram statistics Sergey Senozhatsky
2014-01-16  0:56   ` Minchan Kim
2014-01-16  8:46     ` Sergey Senozhatsky
2014-01-16  9:41       ` Jerome Marchand
2014-01-15 10:16 ` [PATCHv2 4/4] zram: report failed read and writes stats Sergey Senozhatsky
2014-01-16  0:58   ` Minchan Kim
2014-01-16  9:45     ` Jerome Marchand [this message]

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=52D7AA3F.2030501@redhat.com \
    --to=jmarchan@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=sergey.senozhatsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox