linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] zram: introduce per-device debug_stat sysfs node
Date: Fri, 13 May 2016 17:06:43 +0900	[thread overview]
Message-ID: <20160513080643.GE615@swordfish> (raw)
In-Reply-To: <20160513072006.GA21484@bbox>

On (05/13/16 16:20), Minchan Kim wrote:
> > > > @@ -737,12 +737,12 @@ static int zram_bvec_write(struct zram *zram, struct bio_vec *bvec, u32 index,
> > > >  		zcomp_strm_release(zram->comp, zstrm);
> > > >  		zstrm = NULL;
> > > >  
> > > > -		atomic64_inc(&zram->stats.num_recompress);
> > > > -
> > > >  		handle = zs_malloc(meta->mem_pool, clen,
> > > >  				GFP_NOIO | __GFP_HIGHMEM);
> > > > -		if (handle)
> > > > +		if (handle) {
> > > > +			atomic64_inc(&zram->stats.num_recompress);
> > > >  			goto compress_again;
> > > > +		}


just a small note:

> Although 2 is smaller, your patch just accounts only direct reclaim but my
> suggestion can count both 1 and 2 so isn't it better?

no, my patch accounts 1) and 2) as well. the only difference is that my
patch accounts second zs_malloc() call _EVEN_ if it has failed and we
jumped to goto err (because we still could have done reclaim). the new
version would account second zs_malloc() _ONLY_ if it has succeeded, and
thus possibly reclaim would not be accounted.


recompress:
	compress
	handle = zs_malloc FAST PATH

	if (!handle) {
		release stream
		handle = zs_malloc SLOW PATH

		<< my patch accounts SLOW PATH here >>

		if (handle) {
			num_recompress++  << NEW version accounts it here, only it was OK >>
			goto recompress;
		}

		goto err;    << SLOW PATH is not accounted if SLOW PATH was unsuccessful
	}


	-ss

--
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>

  parent reply	other threads:[~2016-05-13  8:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 13:45 [PATCH] zram: introduce per-device debug_stat sysfs node Sergey Senozhatsky
2016-05-12 23:41 ` Minchan Kim
2016-05-13  1:09   ` Sergey Senozhatsky
2016-05-13  6:23     ` Minchan Kim
2016-05-13  6:58       ` Sergey Senozhatsky
2016-05-13  7:05         ` Sergey Senozhatsky
2016-05-13  7:20           ` Minchan Kim
2016-05-13  7:41             ` Sergey Senozhatsky
2016-05-13  8:06             ` Sergey Senozhatsky [this message]
2016-05-13 23:05               ` Minchan Kim
2016-05-14  3:37                 ` Sergey Senozhatsky

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=20160513080643.GE615@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.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;
as well as URLs for NNTP newsgroup(s).