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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 10 Oct 2007 11:49:58 -0400
From:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To:	"Jupe" <jupejupe@...hpost.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: Ethernet driver problem


On Wed, 10 Oct 2007, Jupe wrote:

> Hi,
>
> I have written an ethernet driver for an ARM based board.
> Linux version: 2.6.20.1
>
> Ping is working fine.
>
> I have written a test server/client application using socket programming
> (TCP).
> After the connection is setup the server sends a file to the client.
>
> When I run server on PC and client on ARM board it works without any
> problem.
>
> BUT if I run server on ARM board and client on PC, it works for some
> time and
> then the speed is drastically reduced. (I am sending 4k of data each
> time.
> after 50 sends it reduces its speed.  This happens always.)
>
> I did some debugging and found that after 50 sends, tcp_sendmsg() is not
> being
> called at the same frequency before slowdown.  Also when my driver
> ether_tx seems to
> be working fine.
>
> But still i am not able to get the reason for this behaviour.  Can
> anyone give hints as to
> why this is happening?
>
>
> Regards
> Jupe
>
> -- 
>  Jupe
>  jupejupe@...hpost.com
>
> -- 
> http://www.fastmail.fm - mmm... Fastmail...

First, does your TCP/IP test application work okay on
a Linux machine that does not use your new driver?

That's the first thing to test.

Next, is auto-negotiation working correctly in your
driver? If you don't have auto-negotiation, have you
set the Ethernet parameters correctly so that BOTH
the server and the client use either full-duplex, or
half-duplex, without mixing them up?

Next, make sure that you are properly handling
transmit retries (handling all possible errors)
in your driver. The transmitter does not want
to drop packets if there is no room in the
device, only the receiver should drop packets
if there are no buffers. You do not want
the TCP/IP replacement algorithm to request
missing packets because this slows everything
down. Again, in the transmitter section
of your driver, consider data precious.


Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.59 BogoMips).
My book : http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ