From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Ashish Srivastava <ashish0srivastava0@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org,
Peter Feiner <pfeiner@google.com>,
linux-mm@kvack.org
Subject: Re: [Bug 117731] New: Doing mprotect for PROT_NONE and then for PROT_READ|PROT_WRITE reduces CPU write B/W on buffer
Date: Tue, 17 May 2016 15:03:57 +0300 [thread overview]
Message-ID: <20160517120357.GE9540@node.shutemov.name> (raw)
In-Reply-To: <CAGoWJG-3-SSkr8CTrjOEBfMtiNEbyeo6ynbnC5FiOiMiy5n8fA@mail.gmail.com>
On Tue, May 17, 2016 at 05:17:23PM +0530, Ashish Srivastava wrote:
> > Test-case for that would be helpful, as normal malloc()'ed anon memory
> > cannot be subject for the bug. Unless I miss something obvious.
>
> I've modified the test-case attached to the bug and now it doesn't use
> malloc()'ed memory but file backed mmap shared memory.
Yes, that's consistent with your analysis.
You can post the patch with my Acked-by.
--
Kirill A. Shutemov
--
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>
next prev parent reply other threads:[~2016-05-17 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-117731-27@https.bugzilla.kernel.org/>
2016-05-06 22:01 ` [Bug 117731] New: Doing mprotect for PROT_NONE and then for PROT_READ|PROT_WRITE reduces CPU write B/W on buffer Andrew Morton
2016-05-09 18:07 ` Peter Feiner
2016-05-16 13:35 ` Kirill A. Shutemov
2016-05-17 11:26 ` Ashish Srivastava
2016-05-17 11:36 ` Kirill A. Shutemov
2016-05-17 11:47 ` Ashish Srivastava
2016-05-17 12:03 ` Kirill A. Shutemov [this message]
2016-05-17 15:51 ` Peter Feiner
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=20160517120357.GE9540@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=ashish0srivastava0@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfeiner@google.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 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.