netdev - sky2 stable in 2.6.12-rc1 (but still performance problem)...

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 PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Feb 2007 11:31:58 +0000
From:	"Daniel J Blueman" <daniel.blueman@...il.com>
To:	"Stephen Hemminger" <shemminger@...l.org>
Cc:	"Linux Netdev" <netdev@...r.kernel.org>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	"Linux Networking" <linux-net@...r.kernel.org>
Subject: sky2 stable in 2.6.12-rc1 (but still performance problem)...

Hi Stephen,

2.6.21-rc1 is the first kernel where my SysKonnect Yukon 2 hardware
with the sky2 v1.13 driver is stable under moderate load. Before a few
GBs of data going over my GigE network quickly with NFSv4 would cause
transmit timeouts previously, but now fine.

I am still observing a performance problem - feels like a wmb() or
some buffer flushing is missing somewhere - disabling processor clock
scaling reduces the problem a bit, but does not eliminate it.

What are your preferred way of checking performance? I think that the
TCP send window can grow enough even if ACKs are delayed due to this
problem, such that TCP does not immediately demonstrate this issue. I
could restrict the window scaling factor, so it would be bound by the
data->ACK round-trip latency, which /should/ be low, but I've been
observing it higher. Maybe I try this.

I'll see what I get with iperf UDP also, since this shows min, max,
avg UDP packet latency IIRC.

Thanks for your great work so far though!
  Dan
-- 
Daniel J Blueman
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html