From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Cc: Nilesh Govindrajan <contact@nileshgr.com>
Subject: Re: [gentoo-user] 32bit or 64bit
Date: Tue, 17 Jul 2012 18:31:27 +0200 [thread overview]
Message-ID: <3200326.C1v6ghYEo5@localhost> (raw)
In-Reply-To: <CAHgBc-ttSH9n_p7CbraCdwdvfTCeambVBb4ph8x4C0j2uVBOXg@mail.gmail.com>
Am Dienstag, 17. Juli 2012, 07:52:08 schrieb Nilesh Govindrajan:
> So the same old query again I guess.
> What architecture should I use for a machine with 3GB RAM and a 64bit
> processor?
>
> I believe 64bit should be given serious consideration only if RAM is gt or
> = 4 GB, even there 32bit is allowable with PAE if I'm not wrong.
>
> So what is recommended? There are as such no special use cases to go 64bit
> for me.
now that I am home: you believe wrong.
There are many good reasons to go 64 bit. Easier memory managment, more
registers. Bigger register. Faster math because of the bigger registers.
There is seriously NUL reasons to use 32bit. Zero. Zilch. Why throw away all
those nice improvements - for nothing in return?
Video-codecs? I haven't seen a video in years that was not playable by 64bit
ffmpeg based players but worked with 32bit. Those who were troublemakers were
also unplayable with 32bit codecs. Flash? Just works. Stable? You bet.
The only use case that might come up is wine - I don't know anything about
that beast. Haven't had any use for it in years.
--
#163933
next prev parent reply other threads:[~2012-07-17 16:33 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 2:22 [gentoo-user] 32bit or 64bit Nilesh Govindrajan
2012-07-17 2:39 ` [gentoo-user] " »Q«
2012-07-17 2:52 ` [gentoo-user] " Mark Knecht
2012-07-17 3:04 ` Michael Mol
2012-07-17 3:29 ` Mark Knecht
2012-07-17 4:23 ` Michael Mol
2012-07-17 14:18 ` Mark Knecht
2012-07-17 14:32 ` Michael Mol
2012-07-18 11:20 ` Neil Bothwick
2012-07-17 13:36 ` Pandu Poluan
2012-07-17 13:49 ` Leiking
2012-07-17 14:04 ` Nilesh Govindrajan
2012-07-17 16:34 ` Volker Armin Hemmann
2012-07-17 3:36 ` Bill Kenworthy
2012-07-17 4:25 ` Michael Mol
2012-07-17 6:25 ` J. Roeleveld
2012-07-17 7:05 ` Volker Armin Hemmann
2012-07-17 8:57 ` [gentoo-user] " Nikos Chantziaras
2012-07-17 16:31 ` Volker Armin Hemmann [this message]
2012-07-17 16:38 ` [gentoo-user] " Michael Mol
2012-07-17 16:43 ` Alecks Gates
2012-07-17 20:57 ` [gentoo-user] " Nikos Chantziaras
2012-07-17 21:14 ` Alecks Gates
2012-07-19 12:55 ` Nikos Chantziaras
2012-07-19 13:03 ` Michael Mol
2012-07-19 13:31 ` Nikos Chantziaras
2012-07-19 13:43 ` Alan McKinnon
2012-07-19 13:53 ` Michael Hampicke
2012-07-19 14:06 ` Michael Mol
2012-07-19 14:14 ` Nikos Chantziaras
2012-07-19 14:33 ` Michael Mol
2012-07-19 21:42 ` Alan McKinnon
2012-07-17 21:21 ` Paul Hartman
[not found] ` <CAHgBc-sQm0VVUGHWG8E2q=DGKs_iaMHsmw1-5s-F7ozvX_vsKg@mail.gmail.com>
2012-07-18 2:19 ` Nilesh Govindrajan
2012-07-17 16:44 ` [gentoo-user] " Mark Knecht
2012-07-17 18:13 ` Michael Hampicke
2012-07-17 18:23 ` Mark Knecht
2012-07-17 18:32 ` Michael Mol
2012-07-17 18:47 ` Michael Hampicke
2012-07-17 18:49 ` Mark Knecht
2012-07-17 18:58 ` Michael Mol
2012-07-17 19:18 ` Mark Knecht
2012-07-19 5:34 ` J. Roeleveld
2012-07-19 12:57 ` Mark Knecht
2012-07-19 16:30 ` Volker Armin Hemmann
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=3200326.C1v6ghYEo5@localhost \
--to=volkerarmin@googlemail.com \
--cc=contact@nileshgr.com \
--cc=gentoo-user@lists.gentoo.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