> 
> Why is this an advantage?
> 

currently we access gdb using tcp, a work in progress uses pipes instead of
tcp, eg.
(gdb) target remote | openocd --pipe

This is much faster than tcp and cutting down the traffic is a step.

> 
> I'd want to see some measurements showing that this is an improvement.
> 

from the tests i have done it is either the same or slightly quicker.
It largely depends on the data being read from the target.

> It's a performance regression for embedded hosts as it 
> currently stands.
> 

without testing we will never know for sure, but you may be correct.
The problem is only you have access to a supported emebedded host, so i
cannot test.

> The current code for sending data from the gdb_server to GDB 
> has been optimized for the common code path, so you'll find 
> that it is harder to beat than you might think.
> 
> Also, the patch replaces tested code...
>

This only replaces the openocd->gdb write code, rle support is only from
gdbserver to gdb.
does not work the other way, so gdb->openocd writes are not effected.
 
> 
> The ack, checksum and escape char-less protocol would improve 
> things I think(you mentioned some work in progress over on 
> the gdb development mailing list).
> 

If that patch is accepted then it will be supported.

Cheers
Spen

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to