From: Andy Isaacson <adi@hexapodia.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: avoiding dirty code pages with fixups
Date: Fri, 6 Feb 2004 21:03:43 -0600 [thread overview]
Message-ID: <20040207030343.GB21565@hexapodia.org> (raw)
In-Reply-To: <20040207001317.GE12503@mail.shareable.org>
On Sat, Feb 07, 2004 at 12:13:17AM +0000, Jamie Lokier wrote:
> > The downside is the additional computation on page-in.
>
> > It is a function of how many fixups there are per page, and of how
> > much work ld.so does to satisfy a fixup. I don't have a good feel
> > for how expensive ld.so's fixup mechanism is... any comments?
>
> The other downside of your idea is that every instance of a program
> has more dirty pages. While it is true that the pages do not require
> disk I/O, they still take up RAM that could be used for other page
> cache things.
Well, in the case I describe, currently they're done with MAP_PRIVATE
mappings, so it's no net loss.
-andy
next prev parent reply other threads:[~2004-02-07 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 22:54 Andy Isaacson
2004-02-07 0:13 ` Jamie Lokier
2004-02-07 3:03 ` Andy Isaacson [this message]
2004-02-07 3:33 ` Jamie Lokier
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=20040207030343.GB21565@hexapodia.org \
--to=adi@hexapodia.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®