Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #5337
| From | Bonita Montero <Bonita.Montero@gmail.com> |
|---|---|
| Newsgroups | comp.programming.threads |
| Subject | Re: Understanding page faults and memory swap-in/outs: when should you worry? |
| Date | 2019-12-02 20:05 +0100 |
| Organization | albasani.net |
| Message-ID | <qs3n9n$q8p$1@news.albasani.net> (permalink) |
| References | <900bc8ee-198c-4ed5-a535-3d14bffd8330@googlegroups.com> |
The writer of this article seems a bit confused:
1. Copy on write isn't made on any memory that is allocated.
Memory that is allocated is simply overcommited, that has
nothing to do with copy on write.
2. It's not generally a problem if the virtual address-space
of all processes is larger than the pyhsical memory. It may
be that there are a lot of not written pages which haven't
been associated with individual pyhsical pages. In this case
there's a large overcommit-space.
Back to comp.programming.threads | Previous | Next — Previous in thread | Find similar | Unroll thread
Understanding page faults and memory swap-in/outs: when should you worry? aminer68@gmail.com - 2019-12-02 10:43 -0800 Re: Understanding page faults and memory swap-in/outs: when should you worry? Bonita Montero <Bonita.Montero@gmail.com> - 2019-12-02 20:05 +0100
csiph-web