lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 27 Sep 2022 14:26:19 -0700 From: John Hubbard <jhubbard@...dia.com> To: Chih-En Lin <shiyn.lin@...il.com>, Nadav Amit <namit@...are.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Qi Zheng <zhengqi.arch@...edance.com>, David Hildenbrand <david@...hat.com>, Matthew Wilcox <willy@...radead.org>, Christophe Leroy <christophe.leroy@...roup.eu>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, Luis Chamberlain <mcgrof@...nel.org>, Kees Cook <keescook@...omium.org>, Iurii Zaikin <yzaikin@...gle.com>, Vlastimil Babka <vbabka@...e.cz>, William Kucharski <william.kucharski@...cle.com>, "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>, Peter Xu <peterx@...hat.com>, Suren Baghdasaryan <surenb@...gle.com>, Arnd Bergmann <arnd@...db.de>, Tong Tiangen <tongtiangen@...wei.com>, Pasha Tatashin <pasha.tatashin@...een.com>, Li kunyu <kunyu@...china.com>, Anshuman Khandual <anshuman.khandual@....com>, Minchan Kim <minchan@...nel.org>, Yang Shi <shy828301@...il.com>, Song Liu <song@...nel.org>, Miaohe Lin <linmiaohe@...wei.com>, Thomas Gleixner <tglx@...utronix.de>, Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Andy Lutomirski <luto@...nel.org>, Fenghua Yu <fenghua.yu@...el.com>, Dinglan Peng <peng301@...due.edu>, Pedro Fonseca <pfonseca@...due.edu>, Jim Huang <jserv@...s.ncku.edu.tw>, Huichun Feng <foxhoundsk.tw@...il.com> Subject: Re: [RFC PATCH v2 9/9] mm: Introduce Copy-On-Write PTE table On 9/27/22 12:53, Chih-En Lin wrote: > I'm not familiar with THP right now. But we have a plan for looking > at it to see what will happen with COW PTE. > Currently, I can only say that I prefer to avoid involving the behavior > of huge-page/THP. If there are any ideas here please tell us. > In order to be considered at all, this would have to at least behave correctly in the presence of THP and hugetlbfs, IMHO. Those are no longer niche features. thanks, -- John Hubbard NVIDIA
Powered by blists - more mailing lists