Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1284566
| From | Daniel Micay <danielmicay@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 00/13] MADV_FREE support |
| Date | 2015-12-05 17:00 +0100 |
| Message-ID | <qCnpD-2Wd-7@gated-at.bofh.it> (permalink) |
| References | <qqV3I-27u-7@gated-at.bofh.it> <qCj2F-kX-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 05/12/15 06:10 AM, Pavel Machek wrote: > On Wed 2015-11-04 10:25:54, Minchan Kim wrote: >> MADV_FREE is on linux-next so long time. The reason was two, I think. >> >> 1. MADV_FREE code on reclaim path was really mess. > > Could you explain what MADV_FREE does? > > Comment in code says 'free the page only when there's memory > pressure'. So I mark my caches MADV_FREE, no memory pressure, I can > keep using it? And if there's memory pressure, what happens? I get > zeros? SIGSEGV? You get zeroes. It's not designed for that use case right now. It's for malloc implementations to use internally. There would need to be a new feature like MADV_FREE_UNDO for it to be usable for caches and it may make more sense for that to be a separate feature entirely, i.e. have a different flag for marking too (not sure) since it wouldn't need to worry about whether stuff is touched.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH v2 00/13] MADV_FREE support Pavel Machek <pavel@ucw.cz> - 2015-12-05 12:20 +0100 Re: [PATCH v2 00/13] MADV_FREE support Daniel Micay <danielmicay@gmail.com> - 2015-12-05 17:00 +0100
csiph-web