From: Neil Horman <nhorman@tuxdriver.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] add free hugepage function
Date: Thu, 30 Oct 2014 06:18:56 -0400 [thread overview]
Message-ID: <20141030101856.GA24783@hmsreliant.think-freely.org> (raw)
In-Reply-To: <20141030032324.GC3286@mhcomputing.net>
On Wed, Oct 29, 2014 at 08:23:25PM -0700, Matthew Hall wrote:
> On Wed, Oct 29, 2014 at 11:32:12AM -0400, Neil Horman wrote:
> > >
> > Well, abnormal termination results in abnormal consequences. You expect
> > garbage to get left behind of a program crashes, so I wouldn't really worry
> > about that too much. If you really wanted to you can register chained handlers
> > for SIGSEGV/SIGBUS/etc to catch those conditions, but honestly, that seems like
> > overkill. If a program that uses shared resources terminates abnormally, its
> > well understood that those shared resources may not get released properly, and
> > manual intervention is required to clean them up
> >
> > Neil
>
> Perhaps true. But also one of the top irritations with POSIX SHMEM. ;)
>
POSIX shared memory defines IPC_RMID for exactly that purpose.
next prev parent reply other threads:[~2014-10-30 10:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 2:54 linhaifeng
2014-10-29 3:27 ` Qiu, Michael
2014-10-29 3:44 ` Matthew Hall
2014-10-29 5:14 ` Linhaifeng
2014-10-29 5:26 ` Qiu, Michael
2014-10-29 6:49 ` Linhaifeng
2014-10-29 10:26 ` Bruce Richardson
2014-10-29 14:27 ` Neil Horman
2014-10-29 15:22 ` Ramia, Kannan Babu
2014-10-29 15:32 ` Neil Horman
2014-10-29 16:47 ` Bruce Richardson
2014-10-30 3:23 ` Matthew Hall
2014-10-30 10:18 ` Neil Horman [this message]
2014-10-30 14:56 ` Matthew Hall
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=20141030101856.GA24783@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.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).