linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sanidhya Kashyap <sanidhya.gatech@gmail.com>
To: linux-mm@kvack.org
Subject: Questions about mm
Date: Sun, 07 Dec 2014 23:24:03 -0500	[thread overview]
Message-ID: <548527E3.6040104@gmail.com> (raw)

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>

             reply	other threads:[~2014-12-08  4:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  4:24 Sanidhya Kashyap [this message]
2014-12-08  7:22 ` Chintan Pandya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=548527E3.6040104@gmail.com \
    --to=sanidhya.gatech@gmail.com \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox