From: Alecks Gates <alecks.g@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: multiple installs
Date: Sat, 09 Feb 2013 16:46:54 -0600 [thread overview]
Message-ID: <1360450014.29908.1.camel@klyde> (raw)
In-Reply-To: <CAC=wYCH6Nv82TMSQ7a-EHHhBsgpAWO_CQiVVT0s2NK7YcXH4Yw@mail.gmail.com>
On Sat, 2013-02-09 at 21:20 +1100, Adam Carter wrote:
> You could install to one of the Athlons, then copy it to the other two
> Athlons and one of the FX machines. Then, reconfigure the FX
> install
> for more CPUs and native -march, recompile world and copy it
> to the
> other two FX machines.
>
>
> Even that might not be worth it. Unless you're using something that
> benefits from the new instructions in the FXes, or requires the
> last .1% performance, a single install on an Athlon and copy onto the
> remaining 5 systems will give you more time for something else. From a
> support point of view the consistency can be a win. Just remember to
> specify the Althlon64 CPU type in the kernel config, but with 8 cores
> max.
>
>
> For the hardware, just select a superset of the two systems
> requirements in your kernel config. If you build as modules any
> superfluous code wont even be loaded.
>
That might even depend on the compiler version anyway. But, I agree.
Building with -march=athlon (I think it's athlon?) on one FX machine and
copying to the rest would be fastest.
--
Alecks Gates <alecks.g@gmail.com>
next prev parent reply other threads:[~2013-02-09 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 19:46 [gentoo-user] multiple installs James
2013-02-09 1:10 ` Walter Dnes
2013-02-09 1:58 ` [gentoo-user] " James
2013-02-09 2:06 ` Alecks Gates
2013-02-09 10:20 ` Adam Carter
2013-02-09 22:46 ` Alecks Gates [this message]
2013-02-10 2:33 ` Adam Carter
2013-02-09 17:21 ` walt
2013-02-11 16:32 ` James
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=1360450014.29908.1.camel@klyde \
--to=alecks.g@gmail.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