As stated from Slackware site:

 

Probably the first thing to mention about the release of

Slackware 13.0 is that it marks our first release with an official

64-bit port!

 

What bearing will this have with future releases of UnRaid?   What new cool features and performance enhancements might this bring?  Since I am not a coder or a developer, I would really like to hear from Tom and other senior power users.

 

That means I'm already running unRaid (4.5beta6) on Slackware 13 (32bit). I've been running the Slackware-Current builds and upgrading my packages twice a week for the past month. It's nice to know it's now officially released.

 

I tried getting unRaid running under Slackware64 without luck. The md kernel drivers compiled fine. The problem was an immediate "file not found" issued when trying to run emhttp. I did not have time to run through tracing to see what the exact issue was.

 

If unRaid worked under 64bit, the benefits would not be that much for the average user. It may be slightly better performance when accessing memory (not sure if using PAE only affects memory above 4GB or all memory access) and in some specialized applications.

If unRaid worked under 64bit, the benefits would not be that much for the average user. It may be slightly better performance when accessing memory (not sure if using PAE only affects memory above 4GB or all memory access) and in some specialized applications.

 

I'm going to agree here.  PAE supposedly has a 10% performance penalty. With 8G of ram and a 2.66Ghz processor clocked down to 1.6ghz I have not felt any penalty.

The CPU is mostly idle unless rtorrent is doing a hash check.

 

That means I'm already running unRaid (4.5beta6) on Slackware 13 (32bit). I've been running the Slackware-Current builds and upgrading my packages twice a week for the past month. It's nice to know it's now officially released.

 

I tried getting unRaid running under Slackware64 without luck. The md kernel drivers compiled fine. The problem was an immediate "file not found" issued when trying to run emhttp. I did not have time to run through tracing to see what the exact issue was.

 

If unRaid worked under 64bit, the benefits would not be that much for the average user. It may be slightly better performance when accessing memory (not sure if using PAE only affects memory above 4GB or all memory access) and in some specialized applications.

 

If you were already running Unraid on newer builds: Did you experience an improvement over the global lock problem (NIC blocked, if HDs are spinning up etc.)?

I haven't looked into the effect of drives spinning up on network traffic yet. If I get additional free time, I'll try doing some controlled experiments.

 

Slackware 13 uses Linux kernel 2.6.29.6. As far as I know, the Reiser Filesystem drivers have not yet been changed to deal with the BKL (big-kernel-lock). I think that work is going on in the 2.6.31.x line or hasn't been merged into a mainstream branch. It's been a while since I looked at the mailing list to see how progress is going.

 

However, X mode on the Intel GM4500 graphics chip is significantly improved over the 12.2 release.