From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Allow xfer_partial to signal EOF out of band
Date: Thu, 22 Jun 2006 18:13:00 -0000 [thread overview]
Message-ID: <200606221812.k5MICoV7025706@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060622033609.GA28010@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 21 Jun 2006 23:36:09 -0400)
> Date: Wed, 21 Jun 2006 23:36:09 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> This patch adds a mechanism for to_xfer_partial to signal that it's done.
> I didn't implement the new mechanism for any other targets besides remote;
> it could easily be done for e.g. procfs_read_auxv, but the turnaround time
> is such that it's not a big deal either way. For the remote protocol,
> where there's an extra round trip to the remote link, I set *no_more if
> the target tells me to.
I don't like this at all. I think target_read_partial already has
enough arguments. And having read-like function calls return zero on
EOF is a well-established practice.
> Any comments on this? Otherwise, I'll commit it after qXfer:auxv:read.
> This is the patch which actually saves one packet whenever a remote object
> is transferred.
Does that really impact performance? If it does, I think you should
add some state to the remote protocol and use that to prevent it from
sending a packet.
Mark
next prev parent reply other threads:[~2006-06-22 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 3:36 Daniel Jacobowitz
2006-06-22 18:13 ` Mark Kettenis [this message]
2006-06-22 18:18 ` Daniel Jacobowitz
2006-07-05 19:08 ` 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=200606221812.k5MICoV7025706@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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