Re: [patch 02/20] make the inode i_mmap_lock a reader/writer lock
From: Nick Piggin
Date: Thu Jan 03 2008 - 01:07:42 EST
On Thursday 03 January 2008 10:35, Mike Travis wrote:
> Hi Nick,
> Have you done anything more with allowing > 256 CPUS in this spinlock
> patch? We've been testing with 1k cpus and to verify with -mm kernel,
> we need to "unpatch" these spinlock changes.
Actually I had it in my mind that 64 bit used single-byte locking like
i386, so I didn't think I'd caused a regression there.
I'll take a look at fixing that up now.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/