From: Duncan Hare <dh@synoia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] TCP Patch Set
Date: Wed, 21 Feb 2018 16:39:37 -0800 [thread overview]
Message-ID: <20180221163937.3dbb17bf@raspberrypi> (raw)
In-Reply-To: <CANr=Z=acDhZuXknWQD4EwPLS=qP2tEcMB7Gg5Mbnv+ABuc67=A@mail.gmail.com>
On Mon, 12 Feb 2018 13:35:11 -0600
Joe Hershberger <joe.hershberger@ni.com> wrote:
> >> >>
> >> >> > 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
> >> >> >
> >> >
> >> > 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.
> >
> > Duncan
-----------------------------------------------------------------------
Joe
I'm now at the state where I'm satisfied the selective
acknowledgment implementation is working well, having re-written the
code.
I've transferred 20 4 Mbyte kernels from cloud to desktop without a
failure.
How to proceed?
Issue the patch set again? Or just the TCP module?
Then what's the next step?
Regards
Duncan
next prev parent reply other threads:[~2018-02-22 0:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 2:40 [U-Boot] TCP & Overrrun Duncan Hare
2018-02-08 19:39 ` Joe Hershberger
[not found] ` <820972861.1357945.1518128144239@mail.yahoo.com>
2018-02-08 22:41 ` dh at synoia.com
2018-02-09 2:41 ` Duncan Hare
2018-02-09 21:11 ` Joe Hershberger
[not found] ` <240060435.2566037.1518309545610@mail.yahoo.com>
2018-02-11 0:44 ` Duncan Hare
2018-02-12 19:35 ` Joe Hershberger
2018-02-22 0:39 ` Duncan Hare [this message]
2018-02-22 1:45 ` [U-Boot] TCP Patch Set Joe Hershberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180221163937.3dbb17bf@raspberrypi \
--to=dh@synoia.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox