From: Andrew Lunn <andrew@lunn.ch>
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:17:00 -0000 [thread overview]
Message-ID: <20071219112458.GB5944@lunn.ch> (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
> ### Eclipse Workspace Patch 1.0
> #P ecos
> Index: net/common/current/cdl/net.cdl
> ===================================================================
> RCS file: /cvs/ecos/ecos-opt/net/net/common/current/cdl/net.cdl,v
> retrieving revision 1.17
> diff -u -r1.17 net.cdl
> --- net/common/current/cdl/net.cdl 7 Jan 2007 14:46:55 -0000 1.17
> +++ net/common/current/cdl/net.cdl 19 Dec 2007 10:36:38 -0000
> @@ -167,6 +167,16 @@
> threads can have precedence over TFTP server processing."
> }
>
> + cdl_option CYGPKG_NET_TFTPD_CLIENT_GET_PACKETSIZE {
> + display "TFTP protocol allows negotiation of bigger packets."
> + flavor data
> + default_value 512
> + legal_values 512 to 65464
> + description "
> + tftp blksize egotiation support. >512 byte block sizes improves
> + tftp GET performance"
> + }
You should comment that this requires a server which implements the
optional RFC 2348.
> + if (ntohs(hdr->th_opcode) == OACK) {
> + // We can have only *one* option, the one we sent..
> + if (strncmp(data+2, "blksize", from_len)==0)
> + {
> + blksize=atol(data+2+strlen("blksize")+1);
> + } else
> + {
> + // option ignored, use default.
> + }
> + // Send out the ACK
> + hdr->th_opcode = htons(ACK);
> + hdr->th_block = htons(last_good_block);
> + if (sendto(s, data, 4 /* FIXME */, 0,
> + &from_addr, from_len) < 0) {
> + // Problem sending request
> + *err = TFTP_NETERR;
> + goto out;
> + }
> +
> + }
This should be conditionally compiled.
> + int * const err) {
> + int result;
> +#if CYGPKG_NET_TFTPD_CLIENT_GET_PACKETSIZE>512
> + char *data = malloc(CYGPKG_NET_TFTPD_CLIENT_GET_PACKETSIZE+sizeof(struct tftphdr));
No lines longer than 80 characters please.
You probably need to look at the case of the server returning ERROR
when you pass it the additional option during a get. You probably
should try the GET again without the option and see if it works.
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
next prev parent reply other threads:[~2007-12-19 11:25 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 [this message]
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
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=20071219112458.GB5944@lunn.ch \
--to=andrew@lunn.ch \
--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).