DPDK patches and discussions
 help / color / mirror / Atom feed
From: oulijun <oulijun@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dev <dev@dpdk.org>,
	<linuxarm@openeuler.org>
Subject: Re: [dpdk-dev]  【Some Questions About Multi-Process Resource Cleaning】
Date: Thu, 4 Feb 2021 19:47:01 +0800	[thread overview]
Message-ID: <0aacfa1e-2191-c196-ac73-fad99c016aec@huawei.com> (raw)
In-Reply-To: <8270022.kECihOmdav@thomas>



在 2021/2/4 17:25, Thomas Monjalon 写道:
> Hi,
>
> Sorry your questions are quite confused.
> Please start explaining what is the problem you are trying to solve.
Start the master and slave processes at the same time, and then run the 
kill -9 command to kill the slave processes.
The slave process should call rte_eal_cleanup to release resources. But 
I find that there is no release from the process,
and I think there is a resource leak.
> In general, closing a process does not mean removing the device,
> because it can be used by other processes.
>
>
> 04/02/2021 07:56, oulijun:
>> Hi, Thomas Monjalon&Ferruh Yigit and others
>>
>>       I'm analyzing multiprocess with eal. I have some questions I'd like
>> to ask you.
>>
>> Firstly, After the rte_eal_init() command is executed, the master and
>> slave processes are started successfully.
>>
>> and traffic is continuously sent using the tester.If you run the kill -9
>> command to stop the slave process, restart the re-process, and start
>> packet receiving and sending,
>>
>> how to ensure that the eal resource of the slave process is cleaned up?
>>
>> Second, how to invoke the remove function to clear probe resources of
>> the slave process after the slave process exits?
>>
>> Finally, I found out why the rte_eal_cleanup call was not unregistered
>> mp action after the process exited.
>>
>> I look forward to your response.
>>
>>
>> Thanks
>>
>> Lijun Ou
>>
>>
>>
>
>
>
>
> .
>


  reply	other threads:[~2021-02-04 11:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  6:56 oulijun
2021-02-04  9:25 ` Thomas Monjalon
2021-02-04 11:47   ` oulijun [this message]
2021-02-04 12:29     ` Bruce Richardson
2021-02-04 12:30     ` Thomas Monjalon
2021-02-10 15:59     ` Burakov, Anatoly
2021-03-08  8:56       ` oulijun

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=0aacfa1e-2191-c196-ac73-fad99c016aec@huawei.com \
    --to=oulijun@huawei.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=linuxarm@openeuler.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).