Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: "Yichun Zhang (agentzh)" <agentzh@gmail.com>,
	       gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [python] Optimize python_string_to_host_string() for Python 2.
Date: Tue, 20 Jan 2015 11:13:00 -0000	[thread overview]
Message-ID: <54BE384C.6000605@redhat.com> (raw)
In-Reply-To: <CAB4Tn6MB6tCQ6N6-XEZNBOwEvF-s7oMN=H7mzuhuq1GQfZWuXg@mail.gmail.com>

On 19/01/15 22:08, Yichun Zhang (agentzh) wrote:
> Hello!
>
> On Tue, Jan 13, 2015 at 10:38 PM, Yichun Zhang (agentzh) wrote:
>> With the following patch, my most complicated Python tools
>> finally have comparable performance between Python 2 and
>> Python 3. In the case of Python 2, some real-world Python scripts'
>> overall speedup can be as big as 34% (for my "lgcpath" command [3])
>> or even 57% (for my "lgcstat" command [4]). And from the new Flame
>> Graph [5], we can see that the corresponding function frames are
>> indeed gone.
>>
>> Comments are welcome!
>>
>
> Does the silence in the last 6 days mean that this patch is completely wrong?

Not at all.  I think the post Christmas catch-up has affected patch
review and there is some lag.  I am sure the maintainers will review
your patch soon.

> Actually I have a few more patches to submit to optimize this
> gdb/python part even further. The silence here makes me hesitate ;)

Please submit them. There is no hesitation on commenting on patches
constructively. For my part, I find no issue with people indicating
what might be wrong (or right) with my patches!

> Please let me know if I'm doing something wrong here. Very much appreciated!

You are doing nothing wrong.  Keep pinging your patches. The usual
wait time for pinging a patch is seven days.

Cheers

Phil



  reply	other threads:[~2015-01-20 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14  6:38 Yichun Zhang (agentzh)
2015-01-19 22:08 ` Yichun Zhang (agentzh)
2015-01-20 11:13   ` Phil Muldoon [this message]
2015-01-20 13:13     ` Joel Brobecker
2015-01-20 22:19       ` Yichun Zhang (agentzh)
2015-02-01 23:33 ` Yichun Zhang (agentzh)
2015-02-22 18:01 ` Yichun Zhang (agentzh)
2015-03-03 16:12 ` Joel Brobecker

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=54BE384C.6000605@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=agentzh@gmail.com \
    --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