From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: ?yvind Harboe <oyvind.harboe@zylin.com>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: Improving TFTP performance
Date: Wed, 19 Dec 2007 14:28:00 -0000 [thread overview]
Message-ID: <20071219124104.GA6032@ubuntu> (raw)
In-Reply-To: <c09652430712190238q3f36a54ai96a226983d82635e@mail.gmail.com>
On Wed, Dec 19, 2007 at 11:38:22AM +0100, ?yvind Harboe wrote:
> Take #2. Wrote up negotiation of segsize, passes first smoketest.
> Anyone interesting helping to test/comment on the patch?
>
> Tested w/this server: http://tftpd32.jounin.net
>
> --
> ?yvind Harboe
> http://www.zylin.com - eCos ARM & FPGA developer kit
What can you say about the getting performance? Do you have some results
to show it?
AFAIK, most of *nix guys cannot test this directly. Default TFTP server
for the most Linux distributions was a netkit-tftp. The NetKit tftpd
only supports RFC783. So, they have to install alternate TFTP server
(aka `atftpd'). That is multi-threaded TFTP server which implements all
extensions and multicast: RFC1350, RFC2090, RFC2347, RFC2348, RFC2349.
[RFC]
I would prefer to see in eCos net bag something like `atftp_client.c'
(advanced/alternate) and I would prefer to do not waste those K.I.S.S.
and RFC783 compliant tftp_client.c/tftp_server.c.
Sergei
--
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:[~2007-12-19 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 12:41 [ECOS] " Øyvind Harboe
2007-12-19 13:53 ` [ECOS] " Øyvind Harboe
2007-12-19 14:17 ` Andrew Lunn
2007-12-19 14:47 ` Øyvind Harboe
2007-12-19 15:11 ` Andrew Lunn
2007-12-19 15:34 ` Øyvind Harboe
2007-12-19 22:42 ` Andrew Lunn
2007-12-19 23:39 ` Gary Thomas
2007-12-19 23:52 ` Øyvind Harboe
2007-12-19 14:28 ` Sergei Gavrikov [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=20071219124104.GA6032@ubuntu \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=oyvind.harboe@zylin.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).