From: "Marc Pignat" <marc.pignat@hevs.ch>
To: <eCos Discussion <ecos-discuss@sources.redhat.com>>
Subject: [ECOS] TCP/IP problem
Date: Thu, 26 Sep 2002 23:29:00 -0000 [thread overview]
Message-ID: <sd941319.013@hevs.ch> (raw)
Have you noticed performance problem with tcp/ip ?
When connected throught a switch, there is no problem and with a hub, a small amount of network traffic reduce the performance by a 10 factor...
Has anybody the same problem ?
Marc
=====================================================================
Marc Pignat - Collaborateur Scientifique (Système Intégrés)
Haute Ecole valaisanne
Rte du Rawyl 47
1950 Sion
=====================================================================
Bureau : A306 tél : +41 27 606 8748 fax : +41 27 606 8715 mail : marc.pignat@hevs.ch
Privé : +41 79 678 71 13
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2002-09-27 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 23:29 Marc Pignat [this message]
2002-09-27 5:08 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2001-12-26 5:26 Raman Sivam
2000-09-03 18:45 [ECOS]TCP/IP problem lqx
2000-09-04 4:15 ` Hugo 'NOx' Tyson
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=sd941319.013@hevs.ch \
--to=marc.pignat@hevs.ch \
/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).