qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Todd T. Fries" <qemu-devel@email.fries.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] large memory requirements for translate.c a barrier
Date: Fri, 15 Mar 2013 14:21:20 -0500	[thread overview]
Message-ID: <20130315192120.GF26815@fries.net> (raw)

  PID USERNAME PRI NICE  SIZE   RES STATE     WAIT      TIME    CPU COMMAND
28818 todd      64    0 1142M   53M onproc/0  -         2:01 17.24% cc1

For systems with lower limits on user process memory, this prevents things
from building.

For systems with less physical ram, this presents lots of swapping just to
build the source files.

Is there any hints or hope of breaking translate.c up into a smaller file?

Thanks,
-- 
Todd Fries .. todd@fries.net

 ____________________________________________
|                                            \  1.636.410.0632 (voice)
| Free Daemon Consulting, LLC                \  1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com            \  1.866.792.3418 (FAX)
| PO Box 16169, Oklahoma City, OK 73113      \  sip:freedaemon@ekiga.net
| "..in support of free software solutions." \  sip:4052279094@ekiga.net
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
                                                 
              37E7 D3EB 74D0 8D66 A68D  B866 0326 204E 3F42 004A
                        http://todd.fries.net/pgp.txt

             reply	other threads:[~2013-03-15 19:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 19:21 Todd T. Fries [this message]
2013-03-16  8:14 ` [Qemu-devel] large memory requirements for translate.c a barrier Paolo Bonzini
2013-03-19 15:05   ` qemu-devel
2013-03-21  7:53   ` qemu-devel
2013-03-21  8:25     ` Paolo Bonzini
2013-03-22  7:08       ` qemu-devel
2013-03-22  7:30         ` 陳韋任 (Wei-Ren Chen)
2013-03-22 15:19           ` qemu-devel
2013-03-22 15:28             ` Peter Maydell
2013-03-22  9:34         ` Paolo Bonzini
2013-03-19 15:18 ` Andreas Färber

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=20130315192120.GF26815@fries.net \
    --to=qemu-devel@email.fries.net \
    --cc=qemu-devel@nongnu.org \
    --cc=todd@fries.net \
    /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;
as well as URLs for NNTP newsgroup(s).