linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zhouxianrong <zhouxianrong@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	<akpm@linux-foundation.org>, <sergey.senozhatsky@gmail.com>,
	<minchan@kernel.org>, <iamjoonsoo.kim@lge.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
Date: Sat, 4 Feb 2017 11:33:04 +0800	[thread overview]
Message-ID: <2f856730-512e-7b0b-c0da-8c41305a3ce8@huawei.com> (raw)
In-Reply-To: <20170203153350.GC2267@bombadil.infradead.org>

right, thanks.

On 2017/2/3 23:33, Matthew Wilcox wrote:
> On Fri, Feb 03, 2017 at 04:42:27PM +0800, zhouxianrong@huawei.com wrote:
>> +static inline void zram_fill_page_partial(char *ptr, unsigned int size,
>> +		unsigned long value)
>> +{
>> +	int i;
>> +	unsigned long *page;
>> +
>> +	if (likely(value == 0)) {
>> +		memset(ptr, 0, size);
>> +		return;
>> +	}
>> +
>> +	i = ((unsigned long)ptr) % sizeof(*page);
>> +	if (i) {
>> +		while (i < sizeof(*page)) {
>> +			*ptr++ = (value >> (i * 8)) & 0xff;
>> +			--size;
>> +			++i;
>> +		}
>> +	}
>> +
>> +	for (i = size / sizeof(*page); i > 0; --i) {
>> +		page = (unsigned long *)ptr;
>> +		*page = value;
>> +		ptr += sizeof(*page);
>> +		size -= sizeof(*page);
>> +	}
>> +
>> +	for (i = 0; i < size; ++i)
>> +		*ptr++ = (value >> (i * 8)) & 0xff;
>> +}
>
> You're assuming little-endian here.  I think you need to do a
> cpu_to_le() here, but I don't think we have a cpu_to_leul, only
> cpu_to_le64/cpu_to_le32.  So you may have some work to do ...
>
>
> .
>

  reply	other threads:[~2017-02-04  3:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  8:42 [PATCH] mm: extend zero pages to same element pages for zram zhouxianrong
2017-01-09 23:41 ` Minchan Kim
2017-01-13  4:24   ` Sergey Senozhatsky
2017-01-13  6:23     ` Minchan Kim
2017-01-13  6:36       ` Sergey Senozhatsky
2017-01-13  6:47         ` Minchan Kim
2017-01-13  7:02           ` Sergey Senozhatsky
2017-01-13  8:03             ` Minchan Kim
2017-01-13  8:29 ` zhouxianrong
2017-01-21  8:43   ` Sergey Senozhatsky
2017-01-22  2:58     ` zhouxianrong
2017-01-22  4:45       ` Sergey Senozhatsky
2017-01-23  2:58       ` Joonsoo Kim
2017-01-23  3:32         ` zhouxianrong
2017-01-23  4:03         ` Sergey Senozhatsky
2017-01-23  6:27           ` Joonsoo Kim
2017-01-23  7:13             ` Sergey Senozhatsky
2017-01-23  7:40               ` Minchan Kim
2017-01-24  7:58                 ` zhouxianrong
2017-01-25  1:29                   ` Minchan Kim
2017-01-25  1:32                     ` Sergey Senozhatsky
2017-01-25  2:48                       ` Matthew Wilcox
2017-01-25  4:18                         ` Sergey Senozhatsky
2017-01-25  4:51                           ` Minchan Kim
2017-01-25  5:38                             ` Sergey Senozhatsky
2017-01-25  5:44                               ` Minchan Kim
2017-01-23  6:26       ` Matthew Wilcox
2017-01-23  6:32         ` 答复: " zhouxianrong
2017-02-03  8:34 ` zhouxianrong
2017-02-03  8:42 ` zhouxianrong
2017-02-03 15:33   ` Matthew Wilcox
2017-02-04  3:33     ` zhouxianrong [this message]
2017-02-05 14:21   ` Minchan Kim
2017-02-06  1:28     ` zhouxianrong
2017-02-06 14:14       ` Matthew Wilcox
2017-02-06 23:48       ` Minchan Kim
2017-02-07  2:20         ` zhouxianrong
2017-02-07  2:54           ` Minchan Kim
2017-02-07  3:24             ` zhouxianrong
2017-02-07  4:57               ` 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=2f856730-512e-7b0b-c0da-8c41305a3ce8@huawei.com \
    --to=zhouxianrong@huawei.com \
    --cc=Mi.Sophia.Wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=weidu.du@huawei.com \
    --cc=willy@infradead.org \
    --cc=won.ho.park@huawei.com \
    --cc=zhangshiming5@huawei.com \
    --cc=zhouxiyu@huawei.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).