lkml.org 
[lkml]   [2001]   [Feb]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH] nfsd + scalability
On Thursday February 22, markhe@veritas.com wrote:
> On Thu, 22 Feb 2001, Neil Brown wrote:
> >
> > Certainly I would like to not hold the BKL so much, but I'm curious
> > how much effect it will really have. Do you have any data on the
> > effect of this change?
>
> Depends very much on the hardware configuration, and underlying
> filesystem.
> On an I/O bound system, obviously this has little effect.
>
> Using a filesystem which has a quite deep stack (CPU cycle heavy),
> this is a big win. I've been running with this for so long that I can't
> find my original data files at the moment, but it was around +8%
> improvment in throughput for a 4-way box under SpecFS with vxfs as the
> underlying filesystem. Less benefit for ext2 (all filesystems NFS
> exported "sync" and "no_subtree_check"). Some of the benefit came from
> the fact that there is also a volume manager sitting under the filesystem
> (more CPU cycles with the kernel lock held!).
.... and more ....

Well, you are quite convincing. I am keen to see if I can measure a
performance difference for ext2/raid5, but unfortuantely I don't have
any 4-way boxed (only duals).

If you progress with this can create any patches that do more
interesting things than just drop the lock (e.g. protect the export
table or the read-ahead cache properly), let me know and I will
certainly take them. Meanwhile I will try to find time to have a look
myself.

Thanks,
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.034 / U:0.448 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site