public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Elad Yosef <elad.yosef@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Speed up TFTP download time in RedBoot
Date: Mon, 19 Mar 2012 17:12:00 -0000	[thread overview]
Message-ID: <20120319171120.GB8315@lunn.ch> (raw)
In-Reply-To: <CAOFa9c3Tf-hde5y2FTkFvM_WQX0HTDC7PaK9zFeyqHTH+vyNCg@mail.gmail.com>

On Mon, Mar 19, 2012 at 06:05:36PM +0200, Elad Yosef wrote:
> Hi,
> I'm trying to speed up the TFTP download time in the Redboot.
> I have tried to change the following params;
> 
> CYGNUM_REDBOOT_NETWORKING_MAX_PKTBUF - had no effect
> CYGNUM_REDBOOT_GETC_BUFFER - I have increased it to 10K but still no improvement
> CYGNUM_IO_ETH_DRIVERS_NUM_PKT - had no effect
> 
> My ETH RX ring has 12 buffer each has 770 bytes (9240 in total)
> 
> Am I missing something?

TFTP uses a very simple UDP protocol without any windows. Each
received packet is ACKed before the next is sent. So the size of the
buffers makes no difference, so long as it can hold one frame. You are
only likely to get speedup if you are suffering from packet loss. The
retries are quite slow, so the effect of loosing a packet is quite
big. So make sure you have a reliable network.

You might also want to look at using http instead. I don't know how
good the TCP implementation is in redboot, it might support some
windowing so speeding up the transfer.

	  Andrew


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2012-03-19 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 16:05 Elad Yosef
2012-03-19 17:12 ` Andrew Lunn [this message]
2012-03-19 17:17 ` Stanislav Meduna
2012-03-19 17:44   ` Elad Yosef
2012-03-19 18:12     ` Stanislav Meduna
2012-03-19 18:50       ` Gary Thomas
2012-03-20 11:13         ` Elad Yosef

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=20120319171120.GB8315@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=elad.yosef@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).