From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Won-Kyo Choe <wkyo.choe@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: How to handle page allocation when memory exceeds a local node
Date: Thu, 22 Aug 2019 06:00:01 -0400 [thread overview]
Message-ID: <75574.1566468001@turing-police> (raw)
In-Reply-To: <20190822084121.GA26988@swarm01.ajou.ac.kr>
[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]
On Thu, 22 Aug 2019 17:41:22 +0900, Won-Kyo Choe said:
> In my perspective, if the kernel starts to allocate in the remote node,
> I think the scheduler should move the process to the remote node and it
> will allocate a page in the remote node at first in the loop (in the
> process view, the node would be the local now since it is moved). Would
> the scheduler do that?
That's not the scheduler's job to do that. Plus... what do you do about the
case where a process already has 12G of memory on one node, that node runs out
and 1 4K page gets allocated on another node. Which is better, move the 12G,
or every once in a while try to relocate that 1 4K page to a better node?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-08-22 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 8:41 How to handle page allocation when memory exceeds a local node Won-Kyo Choe
2019-08-22 10:00 ` Valdis Klētnieks [this message]
2019-08-22 10:40 ` Won-Kyo Choe
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=75574.1566468001@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=wkyo.choe@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).