From: Avi Kivity <avi@redhat.com>
To: Kallol Biswas <nucleodyne@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: looking for ideas on VM related research projects
Date: Mon, 08 Jun 2009 09:14:10 +0300 [thread overview]
Message-ID: <4A2CAC32.5030904@redhat.com> (raw)
In-Reply-To: <438397970906072249pe76fafdj49626f20eea31eab@mail.gmail.com>
Kallol Biswas wrote:
> Hi,
> I have a strong team of good, energetic and young kernel engineers
> and research scholar and I am looking for ideas on linux virtual
> memory related research projects for them.
>
> Any input or pointers on future virtual memory projects will be appreciated.
>
>
- automatically using and breaking up large pages
- task/vma affinity
- automatically migrating memory when thread/vma affinity cannot be
satisfied
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-06-08 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 5:49 looking for ideas on VM related research projects Kallol Biswas
2009-06-08 6:14 ` Avi Kivity [this message]
2009-06-09 8:14 ` Kallol Biswas
2009-06-09 8:25 ` Avi Kivity
2009-06-08 21:52 ` Wes Felter
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=4A2CAC32.5030904@redhat.com \
--to=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nucleodyne@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