DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: Qiming Chen <chenqiming_huawei@163.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: slove mbuf leak
Date: Tue, 31 Aug 2021 06:04:26 +0000	[thread overview]
Message-ID: <BN8PR11MB3795F0C7683414108643F520F7CC9@BN8PR11MB3795.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210831032805.5520-1-chenqiming_huawei@163.com>

> -----Original Message-----
> From: Qiming Chen <chenqiming_huawei@163.com>
> Sent: Tuesday, August 31, 2021 11:28
> To: dev@dpdk.org
> Cc: Wang, Haiyue <haiyue.wang@intel.com>; Qiming Chen <chenqiming_huawei@163.com>
> Subject: [PATCH] net/ixgbe: slove mbuf leak
> 
> A local test found that repeated port start and stop operations during
> the continuous SSE vector bufflist receiving process will cause the mbuf
> resource to run out. The final positioning is when the port is stopped,
> the mbuf of the pkt_first_seg pointer is not released. Resources leak.
> The patch scheme is to judge whether the pointer is empty when the port
> is stopped, and release the corresponding mbuf if it is not empty.
> 
> Signed-off-by: Qiming Chen <chenqiming_huawei@163.com>

Backport ?

Cc: stable@dpdk.org

> ---
>  drivers/net/ixgbe/ixgbe_rxtx.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 


Acked-by: Haiyue Wang <haiyue.wang@intel.com>

> 
> --
> 2.30.1.windows.1


  reply	other threads:[~2021-08-31  6:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  3:28 Qiming Chen
2021-08-31  6:04 ` Wang, Haiyue [this message]
2021-08-31  6:40   ` Qiming Chen
2021-08-31  6:51     ` Wang, Haiyue
2021-08-31  8:03 ` [dpdk-dev] [PATCH v2] net/ixgbe: fix " Qiming Chen
2021-08-31  8:06 ` Qiming Chen
2021-08-31 10:00   ` Kevin Traynor
2021-09-01  1:50     ` Qiming Chen
2021-09-01  3:17       ` Wang, Haiyue
2021-09-01  7:22   ` [dpdk-dev] [PATCH v3] " Qiming Chen
2021-09-06  1:22     ` Wang, Haiyue
2021-09-06  1:45       ` Zhang, Qi Z

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=BN8PR11MB3795F0C7683414108643F520F7CC9@BN8PR11MB3795.namprd11.prod.outlook.com \
    --to=haiyue.wang@intel.com \
    --cc=chenqiming_huawei@163.com \
    --cc=dev@dpdk.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 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).