Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1683365
| From | Jerome Glisse <jglisse@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] Protectable memory support |
| Date | 2017-07-07 20:50 +0200 |
| Message-ID | <u0Gue-7RY-7@gated-at.bofh.it> (permalink) |
| References | <tZSQO-6PZ-3@gated-at.bofh.it> <tZSQO-6PZ-1@gated-at.bofh.it> <u0hPc-7Y2-17@gated-at.bofh.it> <u0x7A-1qN-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jul 07, 2017 at 11:42:09AM +0300, Igor Stoppa wrote: > On 06/07/17 19:27, Jerome Glisse wrote: > > On Wed, Jul 05, 2017 at 04:46:26PM +0300, Igor Stoppa wrote: [...] > > Yet another way is to use some of the free struct page fields ie > > when a page is allocated for vmalloc i think most of struct page > > fields are unuse (mapping, index, lru, ...). It would be better > > to use those rather than adding a page flag. > > Like introducing an unnamed union? Some sort of vmalloc_page_subtype? > If that is what you are proposing, I agree that it would work in a > similar fashion as what I have now, but without introducing the overhead > of the extra page flag. No need to introduce unamed union or anything. Just use one of the existing field for install you can make page->mapping point to the pmalloc pool structure. Or you can store a unique key value. I believe there is enough unuse field that for vmalloc pages that you should find one you can use. Just add some documentation in mm_types.h so people are aware of alternate use for the field you are using. Jérôme
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 1/3] Protectable memory support Igor Stoppa <igor.stoppa@huawei.com> - 2017-07-05 15:50 +0200
Re: [PATCH 1/3] Protectable memory support Jerome Glisse <jglisse@redhat.com> - 2017-07-06 18:30 +0200
Re: [PATCH 1/3] Protectable memory support Igor Stoppa <igor.stoppa@huawei.com> - 2017-07-07 10:50 +0200
Re: [PATCH 1/3] Protectable memory support Jerome Glisse <jglisse@redhat.com> - 2017-07-07 20:50 +0200
Re: [PATCH 1/3] Protectable memory support Igor Stoppa <igor.stoppa@huawei.com> - 2017-07-10 17:20 +0200
csiph-web