This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: More generic_load preliminaries
- To: Stan Shebs <shebs at cygnus dot com>
- Subject: Re: More generic_load preliminaries
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Tue, 19 Oct 1999 00:53:54 +1000
- CC: gdb-patches at sourceware dot cygnus dot com
- Organization: Cygnus Solutions
- References: <199910181431.HAA08465@andros.cygnus.com>
Stan Shebs wrote:
>
> From: Andrew Cagney <ac131313@cygnus.com>
> Date: Mon, 18 Oct 1999 19:47:03 +1000
>
> Apart from minor cleanups to generic_load, this patch changes the
> download summary message to:
>
> Transfer rate: 5139 bits/sec, 93 bytes/write.
>
> The ``, 93 bytes/write'' is new.
>
> But what does it mean?? I as a user know about and am interested in
> bits/sec, because I can compare that to nominal baud rate and see how
> well the line is being used. On the other hand, I don't know what
> "bytes/write" means. If I didn't know anything about GDB, I might
> guess that it means calls to write(), that being the only literal
> write operation I know of.
I'll expand on it a little. The main objective is to drop a hint that
new user that perhaphs what they are seeing is sub-optimal. It's like
bits/sec. Seeing 8bits/sec on an ethernet suggests something is broken.
> I suggest putting it on a separate line and adding more explanatory
> material - "output written in multiple chunks, averaging NN
> bytes/chunk" or something like that. Since this potentially comes up
> for every unuspecting embedded user from now on, it's worth giving
> them an extra hint as to what it means.
>
> Is there any reason not to just flush report_transfer_performance?
Eventually, that function is called in more places then you might
expect.
enjoy,
Andrew