From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Run length encoding for gdbserver
Date: Thu, 21 Sep 2006 20:54:00 -0000 [thread overview]
Message-ID: <1158872088.22863.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20060921161239.GA27629@nevyn.them.org>
On Thu, 2006-09-21 at 12:12 -0400, Daniel Jacobowitz wrote:
> The remote protocol supports a simple run length encoding mechanism (in only
> one direction - from the stub to the client). This patch implements it in
> gdbserver. It doesn't make a huge difference to overall performance, but
> can reduce the amount of data sent in some cases by 50%.
This should be a significant gain for libthread_db debugging,
where gdb does a lot of large memory reads behind the scenes.
For stack traces it may not make that much difference, since
those reads are usually small.
Does it work for register packets too?
>
> I realize I didn't leave any room for the equivalent operation in
> the new binary transfer packets in the direction from the client to
> the stub, e.g. for downloading. I don't think this is a big deal.
>
> Tested x86_64-pc-linux-gnu and checked in.
>
next prev parent reply other threads:[~2006-09-21 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 16:12 Daniel Jacobowitz
2006-09-21 20:54 ` Michael Snyder [this message]
2006-09-21 20:57 ` Daniel Jacobowitz
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=1158872088.22863.9.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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