We will be releasing it to the mainline soon. The patches are getting
queued at our end for test and release. It should be out in a couple of
weeks.
Ram
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andi Kleen
Sent: Sunday, August 12, 2007 10:16 AM
Ramkrishna Vepa [EMAIL PROTECTED] writes:
In one of the variations of this driver that is not
released to netdev, the received packets are steered to a channel based
on hashing on a preconfigured criteria such as sockets on tcp_ipv4,
udp_ipv4, tcp_ipv6, udp_ipv6 or addresses in ipv4/6.
Why
Rick Jones wrote:
Sivakumar Subramani wrote:
- Default to IntA interrupt type when there are less than 4 CPUs in
the system.
It might be good to include _why_ in the comment(s). I certainly am
curious to know the reason, and it would be good to have in there for
posterity should the
Sivakumar Subramani wrote:
- Default to IntA interrupt type when there are less than 4 CPUs in the system.
It might be good to include _why_ in the comment(s). I certainly am
curious to know the reason, and it would be good to have in there for
posterity should the underlying conditions
We had found during performance measurement/analysis that with 2 cpus
and napi disabled, and the system transmitting (tcp), the cpus get too
busy due to receive interrupt handling, reducing performance by around
10%.
But then again, when the number of cpus increase, the interrupt scaling
is much
- Default to IntA interrupt type when there are less than 4 CPUs in the system.
Signed-off-by: Sivakumar Subramani [EMAIL PROTECTED]
Signed-off-by: Ramkrishna Vepa [EMAIL PROTECTED]
---
diff -Nurp 2.0.26.2/drivers/net/s2io.c 2.0.26.3/drivers/net/s2io.c
--- 2.0.26.2/drivers/net/s2io.c 2007-08-07
