linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Jerome Marchand <jmarchan@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Nitin Gupta <ngupta@vflare.org>
Subject: Re: [PATCH 1/2] zram: free meta out of init_lock
Date: Wed, 28 Jan 2015 14:35:42 +0900	[thread overview]
Message-ID: <20150128053541.GE32712@blaptop> (raw)
In-Reply-To: <20150128045855.GD32712@blaptop>

On Wed, Jan 28, 2015 at 01:58:55PM +0900, Minchan Kim wrote:
> On Wed, Jan 28, 2015 at 01:50:28PM +0900, Sergey Senozhatsky wrote:
> > On (01/28/15 13:07), Sergey Senozhatsky wrote:
> > > On (01/28/15 12:53), Sergey Senozhatsky wrote:
> > > > > So, I want to go with srcu. Do you agree? or another suggestion?
> > > > 
> > > > yes, I think we need to take a second look on srcu approach.
> > > > 
> > > 
> > > ... or we can ask lockdep to stop false alarming us and leave it as is.
> > > I wouldn't say that ->init_lock is so hard to understand.
> > > just as an option.
> > > 
> > 
> > so... returning back to barriers performance implications.
> > 
> > x86_64, lzo, 4 comp streams, 2G zram, ext4, mount -o rw,relatime,data=ordered
> > 
> >  ./iozone -t 3 -R -r 16K -s 60M -I +Z
> > 
> >        test           base          srcu
> > "  Initial write " 1299639.75   1277621.03
> > "        Rewrite " 2139387.50   2004663.94
> > "           Read " 6193415.00   5091000.00
> > "        Re-read " 6199050.38   4814297.88
> > "   Reverse Read " 4693868.88   4367201.75
> > "    Stride read " 4470633.75   4247550.00
> > "    Random read " 5115339.50   4517352.75
> > " Mixed workload " 4340747.06   3880517.31
> > "   Random write " 1982369.75   1892456.25
> > "         Pwrite " 1352550.22   1248667.78
> > "          Pread " 2853150.06   2445154.41
> > "         Fwrite " 2367397.81   2262384.56
> > "          Fread " 8100746.50   7578071.75
> > 
> > not good.
> > 
> 
> Oops, I never thought it could make mesurable performance.
> I will investigate it.
> 
> Thanks a lot, Sergey!

Sergey, the data is consistent for repeated work?

I tested it with dd on /dev/zram0 without any FS on my KVM
and I cannot see any measureable performance gap.
Hmm, I will try it on real machine.

-- 
Kind regards,
Minchan Kim

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

  reply	other threads:[~2015-01-28  5:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  5:58 [PATCH 1/2] zram: free meta out of init_lock Minchan Kim
2015-01-23  5:58 ` [PATCH 2/2] zram: protect zram->stat race with init_lock Minchan Kim
2015-01-23 13:45   ` Jerome Marchand
2015-01-23 14:38   ` Sergey Senozhatsky
2015-01-24 13:17     ` Ganesh Mahendran
2015-01-25 14:38       ` Sergey Senozhatsky
2015-01-23 13:07 ` [PATCH 1/2] zram: free meta out of init_lock Jerome Marchand
2015-01-23 14:24 ` Sergey Senozhatsky
2015-01-23 14:48   ` Jerome Marchand
2015-01-23 15:47     ` Sergey Senozhatsky
2015-01-26  1:33       ` Minchan Kim
2015-01-26 14:17         ` Sergey Senozhatsky
2015-01-26 16:00           ` Minchan Kim
2015-01-27  2:17             ` Sergey Senozhatsky
2015-01-27  3:18               ` Minchan Kim
2015-01-27  4:03                 ` Sergey Senozhatsky
2015-01-28  0:15                   ` Minchan Kim
2015-01-28  0:22                     ` Minchan Kim
2015-01-28  2:07                       ` Sergey Senozhatsky
2015-01-28  2:57                         ` Minchan Kim
2015-01-28  3:53                           ` Sergey Senozhatsky
2015-01-28  4:07                             ` Sergey Senozhatsky
2015-01-28  4:50                               ` Sergey Senozhatsky
2015-01-28  4:58                                 ` Minchan Kim
2015-01-28  5:35                                   ` Minchan Kim [this message]
2015-01-28  6:08                                     ` Sergey Senozhatsky
2015-01-28  6:10                                       ` Sergey Senozhatsky
2015-01-28  4:55                             ` Minchan Kim
2015-01-28  0:24                     ` Sergey Senozhatsky
2015-01-28  0:59                       ` Minchan Kim
2015-01-26 14:34         ` Jerome Marchand
2015-01-26 15:52           ` Minchan Kim

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=20150128053541.GE32712@blaptop \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=jmarchan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ngupta@vflare.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --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).