From: Elad Yosef <elad.yosef@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Speed up TFTP download time in RedBoot
Date: Tue, 20 Mar 2012 11:13:00 -0000 [thread overview]
Message-ID: <CAOFa9c2oQHMm=dyM2+fcmNz1FxFsnNhd8+k+mAyg8=2h+uGaRQ@mail.gmail.com> (raw)
In-Reply-To: <4F677FBE.50706@mlbassoc.com>
Hi,
I have setup Wire-sharp capture and got about 2 msec between the data
packet and the following ack and again 2 msec delay between the ack
and the following data packet.
I have looked at the fttp code it looks that is not supporting the
"blksize" option as stated in newer RFC.
I would like to to update the tftp code and give it back to eCos.
Where can I get guidance how to?
I'm planing to add option in the CDL file to select the block size.
In case the server does not support "blksize" the client retries to
init session with 512 block size.
Elad
On Mon, Mar 19, 2012 at 8:49 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> On 2012-03-19 12:11, Stanislav Meduna wrote:
>>
>> On 19.03.2012 18:44, Elad Yosef wrote:
>>
>>> I get 108 KBytes/sec after lowering the CYGDBG_REDBOOT_TICK_GRANULARITY
>>> to 50.
>>> I'm downloading SREC image to my target.
>>> I'm using MIPS32 4Kec.
>>> Does any changes to - hal_delay_us(int us) will improve the time?
>>
>>
>> Only if the hal_delay_us does not work as expected. If the throughput
>> significantly depends on the TICK_GRANULARITY in this range
>> I'd check whether the hal_delay_us really waits the time
>> it should.
>>
>> FWIW, I am getting around 200 KB/s using an 80 MHz Cortex-M3
>> processor and the TICK_GRANULARITY of 250 us. I have no experience
>> with MIPS32 but from the description the CPU power shouldn't
>> be an issue here.
>>
>> Note that it can also be the server that is introducing
>> the latencies, especially if it runs on a loaded machine.
>> Or a network driver bug - people usually don't really test
>> the polled mode much.
>>
>> A Wireshark could tell whether it is the client or the
>> server who is introducing latencies and also whether there
>> are any lost packets.
>
>
> Also, the performance will vary greatly, depending on the actual
> networking hardware. I get 1MB/sec on a reasonably fast PowerPC
> (MPC8379), without any special tuning.
>
> --
> ------------------------------------------------------------
> Gary Thomas | Consulting for the
> MLB Associates | Embedded world
> ------------------------------------------------------------
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2012-03-20 11:13 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
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 [this message]
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='CAOFa9c2oQHMm=dyM2+fcmNz1FxFsnNhd8+k+mAyg8=2h+uGaRQ@mail.gmail.com' \
--to=elad.yosef@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gary@mlbassoc.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).