From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6242 invoked by alias); 8 Jul 2005 18:52:38 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6224 invoked by uid 22791); 8 Jul 2005 18:52:35 -0000 Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.196) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 08 Jul 2005 18:52:35 +0000 Received: by rproxy.gmail.com with SMTP id j1so438221rnf for ; Fri, 08 Jul 2005 11:52:33 -0700 (PDT) Received: by 10.11.99.30 with SMTP id w30mr23541cwb; Fri, 08 Jul 2005 11:52:33 -0700 (PDT) Received: by 10.11.99.15 with HTTP; Fri, 8 Jul 2005 11:52:33 -0700 (PDT) Message-ID: <7f45d93905070811522531eb0d@mail.gmail.com> Date: Fri, 08 Jul 2005 18:52:00 -0000 From: Shaun Jackman Reply-To: Shaun Jackman To: gdb@sources.redhat.com, Abatron Support , Ultimate Solutions Support Subject: Re: Loading code with an Abatron BDI2000 In-Reply-To: <7f45d939050708094342de60b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7f45d939050708094342de60b@mail.gmail.com> X-SW-Source: 2005-07/txt/msg00089.txt.bz2 A little searching through GDB's manual turned up "set remote memory-write-packet-size" and "set download-write-size". On my target these values defaulted to 336 and 512 respectively. I found that increasing them to 1025 and 8192 did improve performance somewhat. I used 1025 because I found the TCP packet size sent by GDB was limited to 1024 for some reason unknown to me (anyone else know?) and the "+" acknowledgement was sent in a TCP packet all to its own, but still counted against the memory-write-packet-size. How can I increase the TCP packet size to 1460, the TCP MSS, to get more date bytes out of each packet? Any other thoughts on how else I can improve the transfer rate? Cheers, Shaun set remote memory-write-packet-size 1025 set remote memory-write-packet-size fixed set download-write-size 8192 For the curious, a typical transfer between gdb and the BDI2000 is as follows. The left column is elapsed milliseconds since t0. 0 + 0 $X and 1024 bytes of data 1 ACK the + 3 ACK the $X 14 ACK window update 27 ACK window update 29 + 39 $OK 69 + 70 $X and 1024 bytes of data ... and so forth. There's quite a gap (30 ms) between the BDI's $OK the gdb's +. Could this be improved? On 7/8/05, Shaun Jackman wrote: > I'm using gdb 6.2.1 to debug an ARM7TDMI with an Abatron BDI2000, a > device which speaks the gdb remote protocol natively over Ethernet. > Loading code with gdb is a slower process than I had hoped. ...