From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: [Qemu-devel] Re: memory usage and ioports
Date: Mon, 19 Nov 2007 16:17:26 +0000 [thread overview]
Message-ID: <200711191617.27138.paul@codesourcery.com> (raw)
In-Reply-To: <20071119153421.GH6331@implementation.uk.xensource.com>
On Monday 19 November 2007, Samuel Thibault wrote:
> Samuel Thibault, le Mon 19 Nov 2007 15:20:16 +0000, a écrit :
> > Qemu currently uses 6 65k tables of pointers for handling ioports, which
> > makes 3MB on 64bit machines. There's a comment that says "XXX: use a two
> > level table to limit memory usage". But wouldn't it be more simple and
> > effective to just allocate them through mmap() and when a NULL pointer
> > is read, call the default handlers?
>
> For the ioport_opaque array (500KB on 64bit), it's much simpler, as the
> attached patch suggests.
AFAICS This makes absolutely no difference to memory usage.
Paul
next prev parent reply other threads:[~2007-11-19 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 15:20 [Qemu-devel] memory usage and ioports Samuel Thibault
2007-11-19 15:34 ` [Qemu-devel] " Samuel Thibault
2007-11-19 16:17 ` Paul Brook [this message]
2007-11-19 16:23 ` Samuel Thibault
2008-02-06 14:24 ` [Qemu-devel] [PATCH] " Samuel Thibault
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=200711191617.27138.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@eu.citrix.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 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.