From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751270AbdAYFih (ORCPT ); Wed, 25 Jan 2017 00:38:37 -0500 Received: from mail-pg0-f66.google.com ([74.125.83.66]:35565 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751137AbdAYFif (ORCPT ); Wed, 25 Jan 2017 00:38:35 -0500 Date: Wed, 25 Jan 2017 14:38:49 +0900 From: Sergey Senozhatsky To: Minchan Kim Cc: Sergey Senozhatsky , Matthew Wilcox , zhouxianrong , Joonsoo Kim , linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, sergey.senozhatsky@gmail.com, ngupta@vflare.org, Mi.Sophia.Wang@huawei.com, zhouxiyu@huawei.com, weidu.du@huawei.com, zhangshiming5@huawei.com, won.ho.park@huawei.com Subject: Re: [PATCH] mm: extend zero pages to same element pages for zram Message-ID: <20170125053849.GF2234@jagdpanzerIV.localdomain> References: <20170123040347.GA2327@jagdpanzerIV.localdomain> <20170123062716.GF24581@js1304-P5Q-DELUXE> <20170123071339.GD2327@jagdpanzerIV.localdomain> <20170123074054.GA12782@bbox> <1ac33960-b523-1c58-b2de-8f6ddb3a5219@huawei.com> <20170125012905.GA17937@bbox> <20170125013244.GB2234@jagdpanzerIV.localdomain> <20170125024835.GA24387@bombadil.infradead.org> <20170125041857.GC2234@jagdpanzerIV.localdomain> <20170125045137.GA18289@bbox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170125045137.GA18289@bbox> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (01/25/17 13:51), Minchan Kim wrote: [..] > > Minchan, zhouxianrong, I was completely wrong. we can't > > do memset(). d'oh, I did not know it truncates 4 bytes to > > one byte only (doesn't make too much sense to me). > > Now, I read Matthew's comment and understood. Thanks. > It means zhouxianrong's patch I sent recently is okay? this one looks OK to me https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1316290.html I'd agree with Joonsoo that doing forward prefetching is _probably_ better than backwards prefetching. not that it necessarily should confuse the CPU (need to google if ARM handles it normally), but still. -ss