From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Kyeongdon Kim <kyeongdon.kim@lge.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH 1/3] zram/zcomp: use GFP_NOIO to allocate streams
Date: Tue, 24 Nov 2015 16:10:46 +0900 [thread overview]
Message-ID: <20151124071046.GD7708@blaptop> (raw)
In-Reply-To: <20151124060037.GI705@swordfish>
On Tue, Nov 24, 2015 at 03:00:37PM +0900, Sergey Senozhatsky wrote:
> [..]
> > static struct zcomp_strm *zcomp_strm_alloc(struct zcomp *comp)
> > {
> > - struct zcomp_strm *zstrm = kmalloc(sizeof(*zstrm), GFP_KERNEL);
> > + struct zcomp_strm *zstrm = kmalloc(sizeof(*zstrm), GFP_NOIO);
> > if (!zstrm)
> > return NULL;
> >
> > @@ -85,7 +85,7 @@ static struct zcomp_strm *zcomp_strm_alloc(struct zcomp *comp)
> > * allocate 2 pages. 1 for compressed data, plus 1 extra for the
> > * case when compressed size is larger than the original one
> > */
> > - zstrm->buffer = (void *)__get_free_pages(GFP_KERNEL | __GFP_ZERO, 1);
> > + zstrm->buffer = (void *)__get_free_pages(GFP_NOIO | __GFP_ZERO, 1);
> > if (!zstrm->private || !zstrm->buffer) {
> > zcomp_strm_free(comp, zstrm);
> > zstrm = NULL;
>
> hm... this is not enough.
> we allocate
>
> stream GFP_NOIO
> stream private GFP_KERNEL <<<< still old flags
> stream buffer
>
> so my patch was something like this:
Oops, I missed that. Sorry.
I will include it in next spin.
Thanks!
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2015-11-24 7:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 4:01 [PATCH 1/3] zram/zcomp: use GFP_NOIO to allocate streams Minchan Kim
2015-11-24 4:01 ` [PATCH 2/3] zram: try vmalloc() after kmalloc() Minchan Kim
2015-11-24 4:01 ` [RFC 3/3] zram: pass gfp from zcomp frontend to backend Minchan Kim
2015-11-24 6:00 ` [PATCH 1/3] zram/zcomp: use GFP_NOIO to allocate streams Sergey Senozhatsky
2015-11-24 7:10 ` Minchan Kim [this message]
2015-11-24 6:12 ` [PATCH 2/3] zram: try vmalloc() after kmalloc() Sergey Senozhatsky
2015-11-24 6:42 ` Sergey Senozhatsky
2015-11-24 7:08 ` Minchan Kim
2015-11-24 7:03 ` Minchan Kim
2015-11-24 7:36 ` Sergey Senozhatsky
2015-11-24 7:57 ` Minchan Kim
2015-11-24 8:07 ` Sergey Senozhatsky
2015-11-24 8:14 ` 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=20151124071046.GD7708@blaptop \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kyeongdon.kim@lge.com \
--cc=linux-kernel@vger.kernel.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