From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186])
 by dpdk.org (Postfix) with ESMTP id 202CA6835
 for <dev@dpdk.org>; Thu, 30 Oct 2014 04:15:37 +0100 (CET)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id 10C2580C50B; Wed, 29 Oct 2014 20:23:25 -0700 (PDT)
Date: Wed, 29 Oct 2014 20:23:25 -0700
From: Matthew Hall <mhall@mhcomputing.net>
To: Neil Horman <nhorman@tuxdriver.com>
Message-ID: <20141030032324.GC3286@mhcomputing.net>
References: <1414551269-5820-1-git-send-email-haifeng.lin@huawei.com>
 <533710CFB86FA344BFBF2D6802E60286C7CAAB@SHSMSX101.ccr.corp.intel.com>
 <20141029034437.GA29486@mhcomputing.net>
 <533710CFB86FA344BFBF2D6802E60286C7CB42@SHSMSX101.ccr.corp.intel.com>
 <54508DE1.9090908@huawei.com> <20141029102635.GB8292@BRICHA3-MOBL>
 <20141029142745.GA14253@localhost.localdomain>
 <682698A055A0F44AA47192B20141149711B6074C@BGSMSX102.gar.corp.intel.com>
 <20141029153212.GB14253@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20141029153212.GB14253@localhost.localdomain>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] add free hugepage function
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 03:15:37 -0000

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. ;)