From: Rik van Riel <riel@redhat.com>
To: Daniel Borkmann <dborkman@redhat.com>, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>,
Thomas Hellstrom <thellstrom@vmware.com>,
John David Anglin <dave.anglin@bell.net>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
Carsten Otte <cotte@de.ibm.com>,
Jared Hulbert <jaredeh@gmail.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH akpm] mm: include VM_MIXEDMAP flag in the VM_SPECIAL list to avoid m(un)locking
Date: Mon, 17 Feb 2014 10:06:40 -0500 [thread overview]
Message-ID: <53022580.9010805@redhat.com> (raw)
In-Reply-To: <1392562785-15790-1-git-send-email-dborkman@redhat.com>
On 02/16/2014 09:59 AM, Daniel Borkmann wrote:
> From: Vlastimil Babka <vbabka@suse.cz>
> This patch fixes the issue by adding VM_MIXEDMAP flag to VM_SPECIAL,
> a list of flags that make vma's non-mlockable and non-mergeable.
> The reasoning is that VM_MIXEDMAP vma's are similar to VM_PFNMAP,
> which is already on the VM_SPECIAL list, and both are intended
> for non-LRU pages where mlocking makes no sense anyway. Related
> Lkml discussion can be found in [2].
>
> [1] tools/testing/selftests/net/psock_tpacket
> [2] https://lkml.org/lkml/2014/1/10/427
>
> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> Reported-by: Daniel Borkmann <dborkman@redhat.com>
> Tested-by: Daniel Borkmann <dborkman@redhat.com>
> Cc: Thomas Hellstrom <thellstrom@vmware.com>
> Cc: John David Anglin <dave.anglin@bell.net>
> Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
> Cc: Konstantin Khlebnikov <khlebnikov@openvz.org>
> Cc: Carsten Otte <cotte@de.ibm.com>
> Cc: Jared Hulbert <jaredeh@gmail.com>
> Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Rik van Riel <riel@redhat.com>
> Cc: <stable@vger.kernel.org> [3.11.x+]
Acked-by: Rik van Riel <riel@redhat.com>
--
All rights reversed
next prev parent reply other threads:[~2014-02-17 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1392562785-15790-1-git-send-email-dborkman@redhat.com>
2014-02-16 17:00 ` [PATCH akpm] mm: include VM_MIXEDMAP flag in the VM_SPECIAL list to avoid m(un)locking Hannes Frederic Sowa
2014-02-17 15:06 ` Rik van Riel [this message]
2014-02-18 23:14 ` Andrew Morton
2014-02-19 9:26 ` Vlastimil Babka
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=53022580.9010805@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cotte@de.ibm.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=dave.anglin@bell.net \
--cc=dborkman@redhat.com \
--cc=hannes@stressinduktion.org \
--cc=jaredeh@gmail.com \
--cc=khlebnikov@openvz.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thellstrom@vmware.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.