|To:||Robin Humble <firstname.lastname@example.org>|
|Subject:||Re: Kernel 2.6 for R4600 Indy|
|From:||"Stephen P. Becker" <email@example.com>|
|Date:||Fri, 24 Sep 2004 09:27:44 -0400|
|References:||<4152D58B.firstname.lastname@example.org> <4152E4FC.email@example.com> <firstname.lastname@example.org> <41541B8D.email@example.com> <20040924131734.GC26710@lemming.cita.utoronto.ca>|
|User-agent:||Mozilla Thunderbird 0.8 (Windows/20040913)|
Robin Humble wrote:
On Fri, Sep 24, 2004 at 09:05:17AM -0400, Stephen P. Becker wrote:Heh...I hope you are prepared for a significant slowdown if you end up trying to run n64 userland on such a machine.why's that?
Mostly, 64-bit binaries are much larger than 32-bit. Consider that the scsi controller in an Indy gets about 2mb/sec throughput MAX (on a good day). Also, Indys don't support a large enough memory configuration that 64-bit would be worth it anyhow.
What you would *really* want on such a machine would be n32 userland. You get full 64-bit instructions, but the binaries aren't huge.
|<Prev in Thread]||Current Thread||[Next in Thread>|