| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090513182524.GA20778@merit.edu> Date: Wed, 13 May 2009 14:25:24 -0400 From: Jim Rees <rees@...ch.edu> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Olga Kornievskaia <aglo@...i.umich.edu>, Jeff Moyer <jmoyer@...hat.com>, Jens Axboe <jens.axboe@...cle.com>, linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>, "J. Bruce Fields" <bfields@...ldses.org>, linux-nfs@...r.kernel.org Subject: Re: 2.6.30-rc deadline scheduler performance regression for iozone over NFS Andrew Morton wrote: Jeff's computer got slower. Can we fix that? TCP autotuning can reduce performance by up to about 10% in some cases. Jeff found one of these cases. While the autotuning penalty never exceeds 10% as far as I know, I can provide examples of other cases where autotuning improves nfsd performance by more than a factor of 100. The right thing is to fix autotuning. If autotuning is considered too broken to use, it should be turned off everywhere, not just in nfsd, as it hurts/benefits all TCP clients, not just nfs. This topic has been discussed before on netdev: http://www.spinics.net/lists/netdev/msg68650.html http://www.spinics.net/lists/netdev/msg68155.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists