DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, stephen@networkplumber.org
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
	Dmitry Malloy <dmitrym@microsoft.com>,
	Pallavi Kadam <pallavi.kadam@intel.com>,
	david.marchand@redhat.com, asafp@nvidia.com
Subject: Re: [dpdk-dev] [PATCH v4] eal: detach memsegs on cleanup
Date: Fri, 27 Nov 2020 12:56:42 +0000	[thread overview]
Message-ID: <6ad47d1e-4563-184f-6beb-929e0fea8687@intel.com> (raw)
In-Reply-To: <10371462.e6Z5LZp2yc@thomas>

On 22-Nov-20 6:16 PM, Thomas Monjalon wrote:
> That's a pity we didn't get this patch in DPDK 20.11.
> 
> Anatoly, Stephen, what happened? It is not interesting anymore?
> 
> Anyone else to review?
> 

It is a good patch and should be merged. I wanted to get it into LTS but 
no such luck apparently.

> 
> 20/10/2020 13:53, Thomas Monjalon:
>> Stephen, ping.
>>
>> 15/10/2020 11:54, Burakov, Anatoly:
>>> On 14-Sep-20 2:04 PM, Anatoly Burakov wrote:
>>>> Currently, we don't detach the shared memory on EAL cleanup, which
>>>> leaves the page table descriptors still holding on to the file
>>>> descriptors as well as memory space occupied by them. Fix it by adding
>>>> another detach stage that closes the internal memory allocator resource
>>>> references, detaches shared fbarrays and unmaps the shared mem config.
>>>>
>>>> Bugzilla ID: 380
>>>> Bugzilla ID: 381
>>>>
>>>> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
>>>> ---
>>>
>>> Hi Stephen,
>>>
>>> You were the original submitter for the above bugzilla issues. Could you
>>> please review the patch?
> 
> 
> 


-- 
Thanks,
Anatoly

  reply	other threads:[~2020-11-27 12:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 11:18 [dpdk-dev] [PATCH] " Anatoly Burakov
2020-09-14 11:26 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2020-09-14 11:45   ` [dpdk-dev] [PATCH v3] " Anatoly Burakov
2020-09-14 13:04     ` [dpdk-dev] [PATCH v4] " Anatoly Burakov
2020-10-15  9:54       ` Burakov, Anatoly
2020-10-20 11:53         ` Thomas Monjalon
2020-11-22 18:16           ` Thomas Monjalon
2020-11-27 12:56             ` Burakov, Anatoly [this message]
2020-11-27 13:21               ` Thomas Monjalon
2021-02-11 10:53                 ` Burakov, Anatoly
2021-02-11 16:23       ` Stephen Hemminger
2021-03-03  9:04       ` David Marchand
2021-02-11 13:33   ` [dpdk-dev] [PATCH v2] " Burakov, Anatoly

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=6ad47d1e-4563-184f-6beb-929e0fea8687@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=asafp@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=navasile@linux.microsoft.com \
    --cc=pallavi.kadam@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).