From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] remove download_write_size variable
Date: Tue, 18 Jul 2006 20:42:00 -0000 [thread overview]
Message-ID: <20060718204203.GA27666@nevyn.them.org> (raw)
In-Reply-To: <200607181648.45180.vladimir@codesourcery.com>
On Tue, Jul 18, 2006 at 04:48:44PM +0400, Vladimir Prus wrote:
>
> This patch removes the 'download_write_size'. At the moment, is has pretty low
> value, it's not clear why we need a separate option for just one command, and
> the new qSupported packet allows to negotiate packet size with the stub.
>
> So, I don't see any reason why this variable is needed, and given that flash
> patches will seriously change symfile.c anyway, I suggest that we
> "garbage-collect" this variable.
>
> Comments?
>
> - Volodya
>
> 2006-07-18 Vladimir Prus <vladimir@codesourcery.com>
>
> * symfile.c (download_write_size): Remove.
> (show_download_write_size): Remove.
> (load_section_callback): Don't use download_write_size.
> (_initialize_symfile): Don't register download_write_size.
I can find references to download-write-size on the Internet, e.g. in
FAQs suggesting how to get better write performance. They all seem to
push it as high as memory-write-packet-size, though, which suggests we
do not need both limits.
I think it's reasonable to remove it. However, you'll have to also
remove it from the manual (it's a documented command). And I believe
it should be added to NEWS as a removed feature.
I'm going to let this patch sit a little while, in case anyone else can
think of a reason to keep "set download-write-size".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-18 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 12:48 Vladimir Prus
2006-07-18 20:42 ` Daniel Jacobowitz [this message]
2006-07-31 12:23 ` Vladimir Prus
2006-07-31 17:16 ` Eli Zaretskii
2006-08-01 5:34 ` Vladimir Prus
2006-08-02 3:12 ` Eli Zaretskii
2006-08-08 15:49 ` 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=20060718204203.GA27666@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@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