All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Sagar Abhang <sabhang@brocade.com>
Cc: mtetsuyah@gmail.com, dev@dpdk.org
Subject: Re: [PATCH v2] net/vhost: stop dev in close and address mem leak
Date: Thu, 13 Apr 2017 09:45:42 +0800	[thread overview]
Message-ID: <20170413014542.GD7333@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1491524797-27299-1-git-send-email-sabhang@brocade.com>

On Thu, Apr 06, 2017 at 05:26:37PM -0700, Sagar Abhang wrote:
> Move the call to stop the device inside the close routine because close
> needs to stop the device if it isn't stopped.
> 
> Free the allocated queue buffers in close instead of doing so in remove.
> Original code had these clean ups in remove which was causing memory
> leak.
> 
> Signed-off-by: Sagar Abhang <sabhang@brocade.com>

Applied to dpdk-next-virtio.

	--yliu

      reply	other threads:[~2017-04-13  1:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 22:47 [PATCH] net/vhost: move device stop call in close function Sagar Abhang
2017-04-06  5:51 ` Yuanhan Liu
2017-04-07  0:26   ` [PATCH v2] net/vhost: stop dev in close and address mem leak Sagar Abhang
2017-04-13  1:45     ` Yuanhan Liu [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=20170413014542.GD7333@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=mtetsuyah@gmail.com \
    --cc=sabhang@brocade.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.