From: Bill Jordan <woodennickel@gmail.com>
To: Gleb Natapov <glebn@voltaire.com>
Cc: Hugh Dickins <hugh@veritas.com>,
"Michael S. Tsirkin" <mst@mellanox.co.il>,
Roland Dreier <roland@topspin.com>,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [openib-general] Re: [PATCH repost] PROT_DONTCOPY: ifiniband uverbs fork support
Date: Mon, 15 Aug 2005 12:37:50 -0400 [thread overview]
Message-ID: <5ebee0d10508150937da6c1ed@mail.gmail.com> (raw)
In-Reply-To: <20050811080205.GR16361@minantech.com>
On 8/11/05, Gleb Natapov <glebn@voltaire.com> wrote:
> What about the idea that was floating around about new VM flag that will
> instruct kernel to copy pages belonging to the vma on fork instead of mark
> them as cow?
>
I think the big problem with this idea is the huge memory regions that
InfiniBand applications are dealing with. If the application forks (or
uses system()), you are going to copy a huge chunk of data (most
likely swapping since the application memory footprint is probably
already tuned to consume the available physical memory). And the copy
is really for nothing since in most (or at least many) cases the child
is just going to exec anyway.
--
Bill Jordan
next prev parent reply other threads:[~2005-08-15 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 16:55 [PATCH] fork support Michael S. Tsirkin
2005-07-25 17:19 ` [PATCH repost] PROT_DONTCOPY: ifiniband uverbs " Michael S. Tsirkin
2005-07-26 12:30 ` Hugh Dickins
2005-07-26 13:35 ` Michael S. Tsirkin
2005-08-09 18:13 ` Hugh Dickins
2005-08-10 8:30 ` Michael S. Tsirkin
2005-08-10 8:39 ` [openib-general] " Gleb Natapov
2005-08-10 13:22 ` Hugh Dickins
2005-08-10 13:26 ` Gleb Natapov
2005-08-10 15:27 ` Hugh Dickins
2005-08-11 8:02 ` Gleb Natapov
2005-08-11 14:04 ` Hugh Dickins
2005-08-11 14:07 ` Gleb Natapov
2005-08-11 14:17 ` Hugh Dickins
2005-08-11 14:11 ` Michael S. Tsirkin
2005-08-15 16:37 ` Bill Jordan [this message]
2005-08-16 7:52 ` Gleb Natapov
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=5ebee0d10508150937da6c1ed@mail.gmail.com \
--to=woodennickel@gmail.com \
--cc=glebn@voltaire.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@mellanox.co.il \
--cc=openib-general@openib.org \
--cc=roland@topspin.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