linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chulmin Kim <cmlaika.kim@samsung.com>
To: Dan Streetman <ddstreet@ieee.org>, Alexandr <sss123next@list.ru>
Cc: bugzilla-daemon@bugzilla.kernel.org, Linux-MM <linux-mm@kvack.org>
Subject: Re: [Bug 192571] zswap + zram enabled BUG
Date: Tue, 24 Jan 2017 23:02:30 -0500	[thread overview]
Message-ID: <2059ec0c-d817-9660-9a16-59fe46f3e3a7@samsung.com> (raw)
In-Reply-To: <CALZtONAtjv1fjfVX2d5MKf2HY-kUtSDvA-m7pDbHW+ry2+OhAg@mail.gmail.com>

On 01/24/2017 03:16 PM, Dan Streetman wrote:
> On Mon, Jan 23, 2017 at 7:03 PM, Alexandr <sss123next@list.ru> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>>
>>> Why would you do this?  There's no benefit of using zswap together
>>> with zram.
>>
>> i just wanted to test zram and zswap, i still not dig to deep in it,
>> but what i wanted is to use zram swap (with zswap disabled), and if it
>> exceeded use real swap on block device with zswap enabled.
>
> I don't believe that's possible, you can't enable zswap for only
> specific swap devices; and anyway, if you fill up zram, you won't
> really have any memory left for zswap to use will you?
>
> However, it shouldn't encounter any BUG(), like you saw.  If it's
> reproducable for you, can you give details on how to reproduce it?
>

Hello. Mr. Streetman.


Regarding to this problem, I have a question on zswap.

Is there any reason that
zswap_frontswap_load() does not call flush_dcache_page()?

The zswap load function can dirty the page mapped to user space (might 
be shareable/writable) which seems exactly the condition mentioned in 
the definition of flush_dcache_page().

I'm thinking that
flush_dcache_page() should be called in the end of zswap_frontswap_load().
Could you review my opinion?

Thanks!
Chulmin 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>
>
>

--
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:[~2017-01-25  4:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-192571-27@https.bugzilla.kernel.org/>
     [not found] ` <bug-192571-27-qFfm1cXEv4@https.bugzilla.kernel.org/>
2017-01-17 20:22   ` Andrew Morton
2017-01-18  1:39     ` Sergey Senozhatsky
2017-01-18  5:58       ` Alexandr
2017-01-19  2:56         ` Dan Streetman
2017-01-24  0:03           ` Alexandr
2017-01-24 20:16             ` Dan Streetman
2017-01-25  4:02               ` Chulmin Kim [this message]
2017-01-26 17:09                 ` Dan Streetman
2017-01-25  6:42               ` Alexandr
2017-01-18 13:17       ` Michal Hocko
2017-01-19  1:36         ` Dan Streetman
2017-01-19  3:00           ` Sergey Senozhatsky
2017-01-19  4:20             ` [PATCH] zswap: change BUG to WARN in zswap_writeback_entry Dan Streetman
2017-01-19  5:15               ` Sergey Senozhatsky
2017-01-19 15:36                 ` Dan Streetman
2017-01-19  4:42             ` [Bug 192571] zswap + zram enabled BUG Dan Streetman

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=2059ec0c-d817-9660-9a16-59fe46f3e3a7@samsung.com \
    --to=cmlaika.kim@samsung.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=ddstreet@ieee.org \
    --cc=linux-mm@kvack.org \
    --cc=sss123next@list.ru \
    /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