All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] PCI: minor performance optimization
Date: Sat, 21 Nov 2015 15:22:08 +0800	[thread overview]
Message-ID: <56501BA0.30205@cn.fujitsu.com> (raw)
In-Reply-To: <20151120152425-mutt-send-email-mst@redhat.com>



On 11/20/2015 09:30 PM, Michael S. Tsirkin wrote:
> On Fri, Nov 20, 2015 at 07:58:01PM +0800, Cao jin wrote:
>>
>>
>> On 11/20/2015 07:26 PM, Michael S. Tsirkin wrote:
>>> On Fri, Nov 20, 2015 at 07:04:07PM +0800, Cao jin wrote:
>>>>
>>>>
>>>> On 11/20/2015 06:45 PM, Michael S. Tsirkin wrote:
>>>>> On Fri, Nov 20, 2015 at 06:45:01PM +0800, Cao jin wrote:
>>>>>
>>>>>> 2. As spec says, each capability must be DWORD aligned, so an optimization can
>>>>>>     be done via Loop Unrolling.
>>>>>
>>>>> Why do we want to optimize it?
>>>>>
>>>>
>>>> For tiny performance improvement via less loop. take pcie express
>>>> capability(60 bytes at most) for example, it may loop 60 times, now we just
>>>> need 15 times, a quarter of before.
>>>
>>> But who cares? This is not a data path operation.
>>
>> It is tiny thing I found when browsing code. When found there are several
>> places looks like this, I think maybe it does good to qemu to do this and
>> CCed to you because it don`t look like a simple trivial patch.
>>
>> So, hey Michael, if you don`t like this kind of optimization, that`t ok,
>> forget it. But I think it make me little confused when determine which kind
>> of patch should be CCed to you.
>
> Optimization patches should normally include performance numbers
> if they are to be merged.
> Try to come up with a benchmark and you will realize that the speed of
> this function has no effect under even half way realistic conditions.
>

Maybe you are right. OK, will send the param check patch to the qemu-trivial

>>>>> .
>>>>>
>>>>
>>>> --
>>>> Yours Sincerely,
>>>>
>>>> Cao Jin
>>> .
>>>
>>
>> --
>> Yours Sincerely,
>>
>> Cao Jin
> .
>

-- 
Yours Sincerely,

Cao Jin

      reply	other threads:[~2015-11-21  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 10:45 [Qemu-devel] [PATCH] PCI: minor performance optimization Cao jin
2015-11-20 10:45 ` Michael S. Tsirkin
2015-11-20 11:04   ` Cao jin
2015-11-20 11:26     ` Michael S. Tsirkin
2015-11-20 11:58       ` Cao jin
2015-11-20 13:30         ` Michael S. Tsirkin
2015-11-21  7:22           ` Cao jin [this message]

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=56501BA0.30205@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.