On Thu, Apr 11, 2013 at 10:16:48AM +0100, Pedro Martelletto wrote: > >Speaking of, I see a lot of int64_max sprinkled throughout, which doesn't > >seem right for 32 bit platforms. > > Hi Ted, > > In tmpfs3.diff there are three uses of INT64_MAX: > > The first, in tmpfs_mount(), concerns the maximum amount of memory (in > bytes) that tmpfs will contemplate. This value is bounded by the numbers > in UVM's uvmexp and by the parameters specified upon mount, if any.
I won't pretend to understand this code all that much, but I'm now running it... and I fully intend to try to run it into the ground, as I've started a full bulk build with /tmp using tmpfs... which means both object files and small work directories go to it. I hope to avoid the mfs issues where once you've hit swap, you never go back. I'll let you know if I see any panics. (amd64, btw).
