From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'Mark Salter' <msalter@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Re: Ctrl-C interrupt problem.
Date: Thu, 16 Nov 2000 19:07:00 -0000 [thread overview]
Message-ID: <B1F6452C89AFD411AE0800A0CC734C23015029@EMAIL1> (raw)
It's much better but it's still 5 times slower than before...
One strange thing is that i cna't exceed 511 bytes/write where before i
could go up to about 1500.
I can't see why download speed would suffer from your patch, the only reason
I see is some change in GDB beteween 5.0 and cvs. Do you know if there was
some change ? Some limitation for the 511 bytes/write?
Thanks
--
Fabrice Gautier
fabrice_gautier@sdesigns.com
next reply other threads:[~2000-11-16 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 19:07 Fabrice Gautier [this message]
2000-11-17 6:58 ` Mark Salter
-- strict thread matches above, loose matches on Subject: below --
2000-11-20 16:42 Fabrice Gautier
2000-11-17 12:21 Fabrice Gautier
2000-11-16 12:17 Fabrice Gautier
2000-11-16 17:40 ` Mark Salter
2000-11-15 20:46 [ECOS] " Fabrice Gautier
2000-11-15 23:10 ` [ECOS] " Fernando Nasser
2000-11-16 5:24 ` Mark Salter
2000-11-16 5:48 ` Fernando Nasser
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=B1F6452C89AFD411AE0800A0CC734C23015029@EMAIL1 \
--to=fabrice_gautier@sdesigns.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=msalter@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).