From: Paolo Bonzini <pbonzini@redhat.com>
To: Siddharth Gupta <siddharthgupta04@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] BitsSizedTasks-LargeFrames
Date: Fri, 11 Mar 2016 16:54:55 +0100 [thread overview]
Message-ID: <56E2EA4F.3020803@redhat.com> (raw)
In-Reply-To: <CALwKnOgaM2AKdHX+tJ8vh17rh3Hdd4uqdVBCZ=su-Asi=0eL_A@mail.gmail.com>
Hi Siddharth,
because you are touching possibly "hot" code paths, it is not possible
to just move the allocation to the heap. You will have to check whether
the number of used items is low enough and, if not, switch from the
stack-allocated array to the heap. This way the stack-allocated array
can be made smaller (e.g. 2K).
Thanks,
Paolo
On 11/03/2016 15:50, Siddharth Gupta wrote:
>
prev parent reply other threads:[~2016-03-11 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 14:50 [Qemu-devel] [PATCH] BitsSizedTasks-LargeFrames Siddharth Gupta
2016-03-11 15:50 ` Bastian Koppelmann
2016-03-11 17:45 ` Eric Blake
2016-03-11 15:54 ` Paolo Bonzini [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=56E2EA4F.3020803@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=siddharthgupta04@gmail.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;
as well as URLs for NNTP newsgroup(s).