DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhangkun (K)" <zhang.zhangkun@huawei.com>
To: Masaru Oki <m-oki@stratosphere.co.jp>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Are there considerations about resource recycling by the process, not by the OS?
Date: Fri, 5 Sep 2014 03:39:57 +0000	[thread overview]
Message-ID: <0FCB215400789046A95ECE23C3E46C515F958EFE@szxema505-mbx.china.huawei.com> (raw)
In-Reply-To: <CAFLKUzJnpYV7=fZ-hDYWTa4Ro2OfdqGe9maZM-xLnLSJmEGmnA@mail.gmail.com>

Hi,
    Yes, the program is running as root.
    I want to know if or not the DPDK Community considers about resource recycling.

From: Masaru Oki [mailto:m-oki@stratosphere.co.jp]
Date: 2014年9月5日 11:18
To: Zhangkun (K)
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Are there considerations about resource recycling by the process, not by the OS?

Hi,

you may try
 $ gdb your_program
 gdb> b rte_panic
 gdb> run
 stopped at rte_panic
 gdb> bt

sorry, it is not answer for your question.
by the way, do you run the program as root?


2014-09-05 12:07 GMT+09:00 Zhangkun (K) <zhang.zhangkun@huawei.com<mailto:zhang.zhangkun@huawei.com>>:
Hi,
   I develop the program with the use of dpdk and the process is core dump when the program is started.
The process is crash in case of initing memory failed and calling rte_panic function.
 I search all rte_panic function in the dpdk, and find it so many. Therefore, in case the pr ocess happen fail,
it will abort. The resource allocated before is not released by the process, but by the OS system.
So I have a question: Are there considerations about resource recycling by the process, not by the OS ?


  reply	other threads:[~2014-09-05  3:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  3:07 Zhangkun (K)
2014-09-05  3:17 ` Masaru Oki
2014-09-05  3:39   ` Zhangkun (K) [this message]
2014-09-05  8:18     ` Richardson, Bruce
2014-09-05  9:32     ` Tetsuya.Mukawa

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=0FCB215400789046A95ECE23C3E46C515F958EFE@szxema505-mbx.china.huawei.com \
    --to=zhang.zhangkun@huawei.com \
    --cc=dev@dpdk.org \
    --cc=m-oki@stratosphere.co.jp \
    /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).