All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun.sharma@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Fwd: Re: Virtual memory leaking through IA32 emulation layer for
Date: Thu, 11 Mar 2004 00:30:29 +0000	[thread overview]
Message-ID: <404FB325.9040502@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 49 bytes --]


[ I mistyped the email address for linux-ia64 ]

[-- Attachment #2: Re: Virtual memory leaking through IA32 emulation layer for mmap   and munmap --]
[-- Type: message/rfc822, Size: 3657 bytes --]

From: David Mosberger <davidm@napali.hpl.hp.com>
To: Arun Sharma <arun.sharma@intel.com>
Cc: davidm@hpl.hp.com, linux-ia64@vger.intel.com
Subject: Re: Virtual memory leaking through IA32 emulation layer for mmap and munmap
Date: Wed, 10 Mar 2004 11:44:52 -0800
Message-ID: <16463.28724.277502.132751@napali.hpl.hp.com>

>>>>> On Wed, 10 Mar 2004 11:31:50 -0800, Arun Sharma <arun.sharma@intel.com> said:

  Arun> Yes, I'd really like to see this problem fixed. I think, the
  Arun> patch needs to be as memory efficient as possible - we're
  Arun> using non-pageable kernel memory. So some numbers on the two
  Arun> level bitmap scheme vs keeping lists of head/tail pages for
  Arun> common ia32 workloads would be good.

Agreed.  The good news is that the track is only needed for parially
allocated pages, so the overhead should, in the worst-case, be
proportional to the number of vmareas, not to the amount of memory
mapped.

	--david

                 reply	other threads:[~2004-03-11  0:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=404FB325.9040502@intel.com \
    --to=arun.sharma@intel.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.