From: Doug Evans <dje@google.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Gary Benson <gbenson@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Make remote transfers interruptible
Date: Wed, 12 Aug 2015 17:40:00 -0000 [thread overview]
Message-ID: <CADPb22QnizCi7wAv-21yieRnOyWrEx81iVn6SVFA2PW6dad3Pg@mail.gmail.com> (raw)
In-Reply-To: <55CB8300.3060004@codesourcery.com>
On Wed, Aug 12, 2015 at 10:31 AM, Sandra Loosemore
<sandra@codesourcery.com> wrote:
> On 08/12/2015 08:30 AM, Gary Benson wrote:
>>
>> Hi Sandra,
>>
>> Sandra Loosemore wrote:
>>>
>>> On 08/05/2015 09:28 AM, Gary Benson wrote:
>>>>
>>>> This commit makes it possible to interrupt slow remote file transfers.
>>>>
>>>> gdb/ChangeLog:
>>>>
>>>> * gdb_bfd.c (gdb_bfd_iovec_fileio_pread): Add QUIT call.
>>>
>>>
>>> It still does not work for me. :-(
>>
>>
>> Could you please try this newer version and see if it allows you to
>> interrupt the remote transfers?
>
>
> This version still doesn't make the transfer interruptable with ^C. *But*,
> with this patch, the startup time is reduced from 4 minutes to 19 seconds.
> Huh? Is it really transferring the entire file contents, or was the time
> being used for some GDB-side operation that is quadratic or exponential in
> the size of the read requested rather than the actual byte transfer?
> Independently of the ^C issue, I think we need to better understand what is
> going on here and better tune the code on both sides of the RSP for large
> file transfers. Even if a user asks for target-side libraries explicitly, 4
> minutes to transfer one library doesn't provide a good user experience, and
> 19 seconds isn't so great either when you consider that some interactive
> applications link with dozens of GUI or multimedia libraries and not just
> glibc.
Dozens? How about thousands. 1/2 :-)
[just want to make sure such cases are in the mindset of the community]
next prev parent reply other threads:[~2015-08-12 17:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 15:28 [PATCH 0/2] Better handling of slow remote transfers Gary Benson
2015-08-05 15:28 ` [PATCH 2/2] Make remote file transfers interruptible Gary Benson
2015-08-06 18:03 ` Sandra Loosemore
2015-08-11 10:52 ` Gary Benson
2015-08-12 14:30 ` [PATCH] Make remote " Gary Benson
2015-08-12 17:33 ` Sandra Loosemore
2015-08-12 17:40 ` Doug Evans [this message]
2015-08-13 9:10 ` Gary Benson
2015-08-14 18:37 ` Joel Brobecker
2015-08-17 16:00 ` Pedro Alves
2015-08-17 18:54 ` Sandra Loosemore
2015-08-21 15:16 ` [PATCH 2/2] Make remote file " Pedro Alves
2015-08-21 16:23 ` [pushed] " Gary Benson
2015-08-05 15:28 ` [PATCH 1/2] Warn when accessing binaries over RSP Gary Benson
2015-08-11 11:55 ` Andrew Burgess
2015-08-11 14:04 ` Gary Benson
2015-08-13 13:24 ` [PATCH v2] Warn when accessing binaries from remote targets Gary Benson
2015-08-13 15:07 ` Andrew Burgess
2015-08-21 15:41 ` Pedro Alves
2015-08-21 16:23 ` [pushed] " Gary Benson
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=CADPb22QnizCi7wAv-21yieRnOyWrEx81iVn6SVFA2PW6dad3Pg@mail.gmail.com \
--to=dje@google.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sandra@codesourcery.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