Re: [PATCH -next] zram: do not pass rw argument to __zram_make_request()

2014-01-11 Thread Minchan Kim
On Fri, Jan 10, 2014 at 12:00:59PM +0300, Sergey Senozhatsky wrote: > On (01/10/14 16:14), Minchan Kim wrote: > > On Thu, Jan 09, 2014 at 04:23:43PM +0300, Sergey Senozhatsky wrote: > > > Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw() > > > chain, decode it in zram_bvec_rw

Re: [PATCH -next] zram: do not pass rw argument to __zram_make_request()

2014-01-10 Thread Sergey Senozhatsky
On (01/10/14 16:14), Minchan Kim wrote: > On Thu, Jan 09, 2014 at 04:23:43PM +0300, Sergey Senozhatsky wrote: > > Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw() > > chain, decode it in zram_bvec_rw() instead. Besides, this is the place > > where we distinguish READ and WRI

Re: [PATCH -next] zram: do not pass rw argument to __zram_make_request()

2014-01-09 Thread Minchan Kim
On Thu, Jan 09, 2014 at 04:23:43PM +0300, Sergey Senozhatsky wrote: > Do not pass rw argument down the __zram_make_request() -> zram_bvec_rw() > chain, decode it in zram_bvec_rw() instead. Besides, this is the place > where we distinguish READ and WRITE bio data directions, so account zram > RW sta