Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Anton Blanchard <anton@samba.org>
Cc: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Improve performance of large restore commands
Date: Mon, 29 Jul 2013 14:14:00 -0000	[thread overview]
Message-ID: <51F6789B.3090404@redhat.com> (raw)
In-Reply-To: <20130729154457.0e6e6bd7@kryten>

On 07/29/2013 06:44 AM, Anton Blanchard wrote:

> 2013-07-29  Anton Blanchard  <anton@samba.org>
> 
> 	* target.c (memory_xfer_partial): Cap write to 4K

Period at end of sentence.  Might as well write KB :-).

> 
> Index: b/gdb/target.c
> ===================================================================
> --- a/gdb/target.c
> +++ b/gdb/target.c
> @@ -1669,6 +1669,13 @@ memory_xfer_partial (struct target_ops *
>        void *buf;
>        struct cleanup *old_chain;
>  
> +      /* A large write request is likely to be partially satisfied
> +	 by memory_xfer_partial_1. We will continually malloc
> +	 and free a copy of the entire write request for breakpoint
> +	 shadow handling even though we only end up writing a small
> +	 subset of it. Cap writes to 4K to mitigate this.  */

Double space after all periods, not just the last.

> +      len = min(4096, len);

Space before parens:

     len = min (4096, len);

Otherwise OK.

Thanks,
-- 
Pedro Alves


  reply	other threads:[~2013-07-29 14:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 12:09 Anton Blanchard
2013-07-25 17:30 ` Luis Machado
2013-07-25 17:59 ` Pedro Alves
2013-07-29  5:45   ` Anton Blanchard
2013-07-29 14:14     ` Pedro Alves [this message]
2013-07-29 23:25       ` Anton Blanchard
2013-07-30 11:33         ` Pedro Alves
2013-07-31 12:35           ` Anton Blanchard
2013-07-31 14:47             ` Pedro Alves

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=51F6789B.3090404@redhat.com \
    --to=palves@redhat.com \
    --cc=anton@samba.org \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@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