From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problems when aborting tftp transfers
Date: Mon, 02 Aug 2004 14:14:00 -0000 [thread overview]
Message-ID: <1091456094.12336.120.camel@famine> (raw)
In-Reply-To: <20040802140249.GK14248@lunn.ch>
On Mon, 2004-08-02 at 16:02, Andrew Lunn wrote:
> On Mon, Aug 02, 2004 at 03:45:01PM +0200, ?yvind Harboe wrote:
> > On Mon, 2004-08-02 at 15:01, Andrew Lunn wrote:
> > > On Wed, Jul 21, 2004 at 12:47:53PM +0200, ?yvind Harboe wrote:
> > > > I'm seing problems when aborting tftp transfers:
> > > >
> > > > - With CYGSEM_NET_TFTPD_MULTITHREADED == 0, a subsequent tftp transfer
> > > > after an aborted tftp transfer can get "stuck" since the main tftp
> > > > server loop is receiving stale packets and hence e.g. _write_file() is
> > > > invoked for the terminated tftp transfer session(there can be as many as
> > > > a dozen outstanding stale packets, hence tftp can take a *really* long
> > > > time to return to normal operation). Q: Is
> > > > CYGSEM_NET_TFTPD_MULTITHREADED == 0 working as intended for aborted tftp
> > > > transfers?
> > > >
> > > > - I'm not sure this is a problem or just the way tftp works. When I set
> > > > CYGSEM_NET_TFTPD_MULTITHREADED==1, tftp works even if I abort transfers,
> > > > but the current tftp transfer session on the eCos end does not return to
> > > > the main tftp server loop until the current transfer session has
> > > > exhausted its retries.
> > >
> > > I don't follow what you are taking about here. Could you give some
> > > more details, describe how you produce the problems, what goes wrong
> > > and how you would expect it to act.
> >
> > here is what I did:
> >
> > - with CYGSEM_NET_TFTPD_MULTITHREADED=0.
> > - started a tftp transfer from Windows machine
> > - aborted it on the Windows end
>
> Does the M$ end send an error packet to terminate the transfer or
> simply stop sending data packets?
I don't know what ctrl-c does(I haven't got the equipment wired up so I
can't test right now), but surely terminating the process would cause an
error packet not to be transferred?
> > - at this point the tftp server goes back to the main loop and sees
> > multiple tftp transfer initiation requests from the aborted transfer
> > session.
>
> Initiation requests? You mean WRQ packets from the tftp client you
> have just killed?
Yes.
I really don't speak PPP, TCP/IP, Windows and tftp well enough to pick
this apart without more study.
Perhaps this is something that was lingering in the PPP channel or
tcp/ip stack...
> That would be strange.
Setting CYGSEM_NET_TFTPD_MULTITHREADED=1 fixes the problem because the
original port is closed + reopened.
>
> Andrew
--
Øyvind Harboe
http://www.zylin.com
--
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:[~2004-08-02 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 10:52 Øyvind Harboe
2004-08-02 13:01 ` Andrew Lunn
2004-08-02 13:45 ` Øyvind Harboe
2004-08-02 14:02 ` Andrew Lunn
2004-08-02 14:14 ` Øyvind Harboe [this message]
2004-08-02 14:27 ` Andrew Lunn
2004-08-02 14:49 ` [ECOS] Question on wigglers, debugging Redboot in flash for the XScale target in single step mode Krishna Ganugapati
2004-08-02 14:59 ` Gary Thomas
2004-08-02 15:15 ` [ECOS] Question on wigglers, debugging Redboot in flash forthe " Krishna Ganugapati
2004-08-02 15:21 ` Gary Thomas
2004-08-02 16:51 ` [ECOS] Question on wigglers, debugging Redboot in flash fortheXScale " Krishna Ganugapati
2004-08-03 15:59 ` Krishna Ganugapati
2004-08-03 6:40 ` [ECOS] Problems when aborting tftp transfers Øyvind Harboe
2004-08-03 9:49 ` Andrew Lunn
2004-08-03 9:56 ` Øyvind Harboe
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=1091456094.12336.120.camel@famine \
--to=oyvind.harboe@zylin.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.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).