Hi Duncan,
On Sat, Feb 10, 2018 at 6:44 PM, Duncan Hare <d...@synoia.com> wrote:
> On Sun, 11 Feb 2018 00:39:05 +0000 (UTC)
> Duncan Hare <d...@synoia.com> wrote:
>
>> Duncan Hare
>>
>> 714 931 7952
>>
>>
>> ----- Forwarded Message -----
>> From: Joe Hershberger <joe.hershber...@ni.com>
>> To: Duncan Hare <d...@synoia.com>
>> Cc: Joe Hershberger <joe.hershber...@ni.com>; u-boot
>> <u-boot@lists.denx.de> Sent: Friday, February 9, 2018 1:11 PM
>> Subject: Re: [U-Boot] TCP & Overrrun
>>
>> On Thu, Feb 8, 2018 at 8:41 PM, Duncan Hare <d...@synoia.com> wrote:
>> > On Thu, 8 Feb 2018 22:15:44 +0000 (UTC)
>> > Duncan Hare <d...@synoia.com> wrote:
>> >
>> >> Duncan Hare
>> >>
>> >> 714 931 7952
>> >>
>> >>
>> >> ----- Forwarded Message -----
>> >> From: Joe Hershberger <joe.hershber...@ni.com>
>> >> To: Duncan Hare <d...@synoia.com>
>> >> Cc: u-boot <u-boot@lists.denx.de>; Joe Hershberger
>> >> <joe.hershber...@ni.com> Sent: Thursday, February 8, 2018 11:40 AM
>> >> Subject: Re: [U-Boot] TCP & Overrrun
>> >>
>> >> Hi Duncan,
>> >>
>> >> On Wed, Feb 7, 2018 at 8:40 PM, Duncan Hare <d...@synoia.com>
>> >> wrote:
>> >> > I'm gettin overrun on the raspberry pi.
>> >> >
>> >> > Which ethernet drived does it use?
>> >>
>> >> You didn't specify which one you are talking about, but here's how
>> >> to find out...
>> >>
>> >> Assuming rpi3, find the config first...
>> >>
>> >> configs/rpi_3_defconfig says:
>> >> CONFIG_DEFAULT_DEVICE_TREE="bcm2837-rpi-3-b"
>> >> arch/arm/dts/bcm2837-rpi-3-b.dts says: #include
>> >> "bcm283x-rpi-smsc9514.dtsi" arch/arm/dts/bcm283x-rpi-smsc9514.dtsi
>> >> says: ethernet: usbether@1 {
>> >> compatible = "usb424,ec00"; grep -rn ec00 drivers/ says:
>> >> drivers/usb/eth/smsc95xx.c
>> >>
>> >> Cheers,
>> >> -Joe
>> >>
>> >> > I need to determine if it
>> >> > uses CONFIG_SYS_RX_ETH_BUFFER" from net.h and the
>> >> > "net_rx_packets" buffer pool defined in net/net.c
>> >> >
>> >> > grep suggests it is not using net_rx_packets.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Duncan Hare
>> >> > _______________________________________________
>> >> > U-Boot mailing list
>> >> > U-Boot@lists.denx.de
>> >> > https://lists.denx.de/listinfo/u-boot
>> > ___________________________________________________
>> > Joe
>> >
>> > Two solutions:
>> >
>> > Option 1.
>> >
>>
>> I think option 1 is the way to go.
>>
>> Thanks,
>> -Joe
>
> Joe
>
> The overruns were caused by printing error messages. The print
> process is (very) slow compared with packet and computer speeds, and
> causes overruns.
>
> I turned off all the error messages in tcp.c and the overruns also
> stopped.
You could probably make the printing buffered (maybe just turn on such
a thing) to speed it up. You can also have different log levels to
turn on different traces so you can reduce the load for printing.
> Makes debugging harder.
>
> Duncan
>
> _______________________________________________
> U-Boot mailing list
> U-Boot@lists.denx.de
> https://lists.denx.de/listinfo/u-boot
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
