From: Michael Tokarev <mjt@tls.msk.ru>
To: "Li, Zhen-Hua" <zhen-hual@hp.com>
Cc: qemu-trivial@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH 1/1] virtio-blk: Use a req pool instead of malloc/free
Date: Thu, 27 Mar 2014 09:07:53 +0400 [thread overview]
Message-ID: <5333B229.6070603@msgid.tls.msk.ru> (raw)
In-Reply-To: <1395736938-13402-1-git-send-email-zhen-hual@hp.com>
25.03.2014 12:42, Li, Zhen-Hua wrote:
> From: "Li, ZhenHua" <zhen-hual@hp.com>
>
> In virtio-blk module, when there is new request, new req structure
> will be created by malloc. Use a req pool instead of this, will increase
> performance;
Um. This does not qualify neither as a trivial change nor as a stable bugfix.
In my opinion anyway.
Thanks,
/mjt
next prev parent reply other threads:[~2014-03-27 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 8:42 [Qemu-trivial] [PATCH 1/1] virtio-blk: Use a req pool instead of malloc/free Li, Zhen-Hua
2014-03-27 5:07 ` Michael Tokarev [this message]
2014-03-27 8:15 ` [Qemu-devel] [Qemu-stable] " Fam Zheng
-- strict thread matches above, loose matches on Subject: below --
2014-03-26 2:02 [Qemu-trivial] " Li, Zhen-Hua
2014-03-26 2:07 ` Li, ZhenHua
2014-03-26 9:55 ` Paolo Bonzini
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=5333B229.6070603@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=qemu-stable@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhen-hual@hp.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 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.