linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* Questions about mm
@ 2014-12-08  4:24 Sanidhya Kashyap
  2014-12-08  7:22 ` Chintan Pandya
  0 siblings, 1 reply; 2+ messages in thread
From: Sanidhya Kashyap @ 2014-12-08  4:24 UTC (permalink / raw)
  To: linux-mm

Hello everyone,

I have some questions about page allocation and locking.

- Suppose that a process is about to be killed and before that happens, I want
to keep the content of the page intact in the memory, i.e. the page should
neither be zeored or allocated to some other process unless required. In order
to achieve this, what can be the most optimal approach in which the internals of
the kernel is not changed besides adding a syscall or something.

- Another is what happens if I increase the count of mm_users and mm_count
before and later that process gets killed. Assuming that the mm was linked only
to the killed process. What will happen in this case?

- Last question that I wanted to know is what will happen if I change the flags
of the pages to be reserved and unevictable?
Is it possible for the pages to be set pinned as well?
Can this approach help me soling the first issue or I might get a BUG by some
other component in kernel?

Since, I have just started playing with the kernel, so there is a possibility
that I might have asked something very silly/horrific. Please bear with me.

Thanks,
Sanidhya

--
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>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-12-08  7:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-08  4:24 Questions about mm Sanidhya Kashyap
2014-12-08  7:22 ` Chintan Pandya

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox