Re: [Beowulf] new release of GAMMA: x86-64 + PRO/1000

2006-02-04 Thread Greg Lindahl
On Sat, Feb 04, 2006 at 01:51:29PM -0500, Mark Hahn wrote: > well, that's the sticking point, isn't it? is there any way that GAMMA > could be converted to use the netpoll interface? for instance, look at > drivers/net/netconsole.c which is, admittedly, much less ambitious > than supporting MP

Re: [Beowulf] Opteron downrates DDR400 to DDR333 performance?

2006-02-04 Thread Greg Lindahl
On Sat, Feb 04, 2006 at 12:51:46PM -0500, Mark Hahn wrote: > well, FBdimms maintain a high clock, but stretch latency quite a bit as > you add devices. and that's some distance off, I think - rumor has it > that AMD is close to shipping DDR2 support. FBdimms are great for having a of devices o

Re: [Beowulf] new release of GAMMA: x86-64 + PRO/1000

2006-02-04 Thread Tim Mattox
Hello, I have been hoping to find the time to see what it would take to use both the GAMMA and my FNN stuff together. Unfortunately, I've not been able to muster up that free time... As I alluded to in a previous post, I should have my FNN runtime support software available for public consumption

Re: [Beowulf] new release of GAMMA: x86-64 + PRO/1000

2006-02-04 Thread Mark Hahn
> GAMMA only supports the Intel PRO/1000 Gigabit Ethernet NIC (e1000 driver). well, that's the sticking point, isn't it? is there any way that GAMMA could be converted to use the netpoll interface? for instance, look at drivers/net/netconsole.c which is, admittedly, much less ambitious than su

Re: [Beowulf] Opteron downrates DDR400 to DDR333 performance?

2006-02-04 Thread Mark Hahn
>> So you could get 4GB of RAM on a processor if you use >> single ranked DIMMs. perhaps this is TMI, but the answer depends on which cpu rev you're using (and whether the bios optimizes the memory controller.) the AMD bios-writers doc cited earlier shows that 4 dimms (2xdouble, 2xsingle) can sti

Re: [Beowulf] RE: ssh without password for non root user in RedHat Enterprise Linux 3

2006-02-04 Thread Mark Hahn
> I went through this same exercise a while back and it finally ended up > being a permission problem on my home directory (not just the .ssh my first step in solving ssh issues is to look at syslog, which contained a message explaining this. but also, did you try unsetting the StrictModes