From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Doug Evans <dje@google.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Marc Khouzam <marc.khouzam@ericsson.com>,
Greg Law <glaw@undo-software.com>,
Hui Zhu <teawater@gmail.com>
Subject: Re: [patch] only update dcache after write succeeds
Date: Mon, 14 Sep 2009 20:43:00 -0000 [thread overview]
Message-ID: <4AAEAB04.9030302@vmware.com> (raw)
In-Reply-To: <200909142140.09644.pedro@codesourcery.com>
Pedro Alves wrote:
> On Monday 14 September 2009 21:20:38, Michael Snyder wrote:
>
>>> IOW, if some target method does return > 0, then the write succeeded, right?
>>> Are there different kinds of "success" in effect here?
>> Well, maybe only in our case. ;-)
>>
>> If nobody else has any worries about it, I'm OK with it.
>>
>> ----
>> * In our case (process record), it's a bad thing for the target
>> beneath to be called after the user has said "no".
>
> The user is saying "no" to the whole high level operation, not to
> a single partial transfer. In that case, you shouldn't even
> attempt to partial xfer in the target beneath, I would say. A thrown
> error for those cases looks like the way to go. Perhaps even better
> would be to be able to foretell if the transfer is going to be
> problematic and warn/query upfront, but it's hard in some cases.
Agree, "error()" is the way to go here.
next prev parent reply other threads:[~2009-09-14 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 19:17 Doug Evans
2009-09-14 19:26 ` Michael Snyder
2009-09-14 19:29 ` Marc Khouzam
2009-09-14 20:21 ` Michael Snyder
2009-09-14 19:43 ` Doug Evans
2009-09-14 20:20 ` Michael Snyder
2009-09-14 20:40 ` Pedro Alves
2009-09-14 20:43 ` Michael Snyder [this message]
2009-09-14 20:41 ` Doug Evans
2009-09-14 20:45 ` Michael Snyder
2009-09-14 19:26 ` Greg Law
2009-09-14 19:28 ` Marc Khouzam
2009-09-15 0:11 ` Hui Zhu
2009-09-15 6:58 ` Doug Evans
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=4AAEAB04.9030302@vmware.com \
--to=msnyder@vmware.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=glaw@undo-software.com \
--cc=marc.khouzam@ericsson.com \
--cc=pedro@codesourcery.com \
--cc=teawater@gmail.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