public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Guangyu Pei <pei@CS.UCLA.EDU>
To: Gary Thomas <gthomas@cambridge.redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] problem with TCP/IP stack
Date: Fri, 26 Jan 2001 16:39:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.10.10101261633010.19909-100000@k2.cs.ucla.edu> (raw)
In-Reply-To: <XFMail.20010126144559.gthomas@cambridge.redhat.com>

Yes, you are right. I modified one of the test program: udp_lo_test.c
program. Instead of using a loopback address, I use the real IP address.
Thank you,
Gary
On Fri, 26 Jan 2001, Gary Thomas wrote:

|Are you trying to run one of our test/demo programs?  If not, I'm not
|sure I understand your "UDP server" terminology.
|
|On 26-Jan-2001 Gary Guangyu Pei wrote:
|> Hi,
|> I encountered the following problem with TCP/IP stack:
|> It cannot run both UDP server and client together. If I run server only,
|> it can receive UDP packets from the other nodes. However, if I run both
|> client and server, the client can keep on sending out packets, the server
|> will stop receiving packets after it receives the first packet (or
|> sometime the first 2 packets) from a client. I use the gdb to trace the
|> program. I find the received packages travelling along the protocol stack
|> all way up to udp_usrreq.c. After calling the sorwakeup() at line 565, the
|> server thread never gets to run.
|> 
|> Does anyone know what might go wrong? Do you have similar experience?
|> 
|> The network priority is 7. I tried both 6,7,8 priority for the udp server.
|> 
|> Thank you very much, any suggestion is highly appreciated.
|> 
|> Gary
|> 
|

  reply	other threads:[~2001-01-26 16:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 10:47 Gary Guangyu Pei
2001-01-26 13:46 ` Gary Thomas
2001-01-26 16:39   ` Gary Guangyu Pei [this message]
2002-07-18 22:44 [ECOS] Problem with TCP/IP Stack Your Name
2008-01-10 13:09 [ECOS] Problem with TCP/IP stack Antoine Zen-Ruffinen
2008-01-10 13:18 ` Gary Thomas
     [not found]   ` <2cbbd8de0801100544j62d5b5ecl75969aaec1da5122@mail.gmail.com>
2008-01-10 13:55     ` Gary Thomas
2008-01-10 14:15       ` Antoine Zen-Ruffinen
2008-01-10 15:32         ` Antoine Zen-Ruffinen
2008-01-11  8:48           ` Antoine Zen-Ruffinen
2008-01-11 12:38             ` Antoine Zen-Ruffinen
2008-01-11 12:47               ` Gary Thomas
2008-01-11 12:52                 ` Andrew Lunn
2008-01-11 15:43                 ` Antoine Zen-Ruffinen
2008-01-11 15:59                   ` Gary Thomas
2008-01-11 16:08                     ` Antoine Zen-Ruffinen
2008-01-11 16:29                       ` Gary Thomas
2008-01-11 16:38                         ` Antoine Zen-Ruffinen
2008-01-11 16:39                           ` Antoine Zen-Ruffinen
2008-01-11 16:46                             ` Gary Thomas

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=Pine.SOL.4.10.10101261633010.19909-100000@k2.cs.ucla.edu \
    --to=pei@cs.ucla.edu \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gthomas@cambridge.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).