I have, for now, hacked my way around my problem by splitting the server's uplink into two separate bonds. This seems to have moderated the transaction rate of the HPC farm and allowed the "ls -l" calls to be served at an acceptable rate. If someone smart thinks that giving the problem a real solution would be worthwhile, I'd be glad to offer more details about my test setup. Thanks again for the various suggestions offered. Andrew --- On Tue, 4/5/11, Andrew Klaassen <clawsoon@xxxxxxxxx> wrote: > From: Andrew Klaassen <clawsoon@xxxxxxxxx> > Subject: Re: Prioritizing readdirplus/getattr/lookup > To: "Benny Halevy" <bhalevy@xxxxxxxxxxx>, "Jim Rees" <rees@xxxxxxxxx> > Cc: "Garth Gibson" <garth@xxxxxxxxxx>, linux-nfs@xxxxxxxxxxxxxxx > Received: Tuesday, April 5, 2011, 5:06 PM > --- On Tue, 4/5/11, Jim Rees <rees@xxxxxxxxx> > wrote: > > > It would be interesting to see someone who is affected > by > > this implement the readdirplus system call, modify ls > to > > use it, and report the results. I suspect the system > call > > won't go anywhere in linux without some evidence > > that it solves a real problem for real users. > > I can't speak to a readdirplus system call; my own > (admittedly naive) testing suggests that the system calls > are JustFineThankYou, since local "ls -l" with NFS loading > (and vice versa) performs very well. > > What I can say for certain is that whatever NetApp GX is > doing to respond to getattr and lookup calls completely > wipes the floor with whatever the Linux nfsd is doing... > > ...*even when Linux is serving out a completely cached, > completely read-only workload*. > > I wish I had the know-how and intelligence to figure out > exactly why. > > Andrew > > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-nfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
