qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pooja Dhannawat <dhannawatpooja1@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: jasowang@redhat.com, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v5] net: Allocating Large sized arrays to heap
Date: Thu, 31 Mar 2016 16:08:55 +0530	[thread overview]
Message-ID: <CAPAwAwiYfKZw-d4A6fz+qS+mQEWVLhE6qahgk2ED1RPd2iuoLw@mail.gmail.com> (raw)
In-Reply-To: <20160331095849.GB20286@stefanha-x1.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]

On Thu, Mar 31, 2016 at 3:28 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:

> On Mon, Mar 28, 2016 at 06:04:11PM +0530, Pooja Dhannawat wrote:
> > nc_sendv_compat has a huge stack usage of 69680 bytes approx.
> > Moving large arrays to heap to reduce stack usage.
> >
> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> > Signed-off-by: Pooja Dhannawat <dhannawatpooja1@gmail.com>
> > ---
> >  net/net.c | 13 +++++++++----
> >  1 file changed, 9 insertions(+), 4 deletions(-)
> >
> > diff --git a/net/net.c b/net/net.c
> > index b0c832e..663da13 100644
> > --- a/net/net.c
> > +++ b/net/net.c
> > @@ -709,23 +709,28 @@ ssize_t qemu_send_packet_raw(NetClientState *nc,
> const uint8_t *buf, int size)
> >  static ssize_t nc_sendv_compat(NetClientState *nc, const struct iovec
> *iov,
> >                                 int iovcnt, unsigned flags)
> >  {
> > -    uint8_t buf[NET_BUFSIZE];
> > +    uint8_t *buf = NULL;
> >      uint8_t *buffer;
> >      size_t offset;
> > +    ssize_t ret;
> >
> >      if (iovcnt == 1) {
> >          buffer = iov[0].iov_base;
> >          offset = iov[0].iov_len;
> >      } else {
> > +        buf = g_new(uint8_t, NET_BUFSIZE);
> >          buffer = buf;
> > -        offset = iov_to_buf(iov, iovcnt, 0, buf, sizeof(buf));
> > +        offset = iov_to_buf(iov, iovcnt, 0, buf, NET_BUFSIZE);
> >      }
> >
> >      if (flags & QEMU_NET_PACKET_FLAG_RAW && nc->info->receive_raw) {
> > -        return nc->info->receive_raw(nc, buffer, offset);
> > +        ret = nc->info->receive_raw(nc, buffer, offset);
> >      } else {
> > -        return nc->info->receive(nc, buffer, offset);
> > +        ret = nc->info->receive(nc, buffer, offset);
> >      }
> > +
> > +    g_free(buf);
> > +    return ret;
> >  }
> >
> >  ssize_t qemu_deliver_packet_iov(NetClientState *sender,
> > --
> > 2.5.0
>
> CCing Jason Wang, net subsystem maintainer.  Please use
> scripts/get_maintainer.pl to find the right people to CC in future
> patches.
>
> Yes, I am sorry about that. Fam also pointed out this thing but I forgot
this time also.
I will keep that mind from onwards.


> We may also want to keep a smaller stack buffer so that reasonably-sized
> packets (e.g. up to 2 KB) can be send without the performance cost of
> g_malloc().
>

[-- Attachment #2: Type: text/html, Size: 3388 bytes --]

  reply	other threads:[~2016-03-31 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 12:34 [Qemu-devel] [PATCH v5] net: Allocating Large sized arrays to heap Pooja Dhannawat
2016-03-31  9:58 ` Stefan Hajnoczi
2016-03-31 10:38   ` Pooja Dhannawat [this message]
2016-04-01  1:57 ` Jason Wang

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=CAPAwAwiYfKZw-d4A6fz+qS+mQEWVLhE6qahgk2ED1RPd2iuoLw@mail.gmail.com \
    --to=dhannawatpooja1@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).