From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 0F8A37DFC for ; Thu, 30 Oct 2014 15:47:52 +0100 (CET) Received: from android-fb5fc4f6ed62fb42.attlocal.net (99-34-229-174.lightspeed.sntcca.sbcglobal.net [99.34.229.174]) by mail.mhcomputing.net (Postfix) with ESMTPSA id 7439C80C507; Thu, 30 Oct 2014 07:55:40 -0700 (PDT) User-Agent: K-9 Mail for Android In-Reply-To: <20141030101856.GA24783@hmsreliant.think-freely.org> 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> <20141030032324.GC3286@mhcomputing.net> <20141030101856.GA24783@hmsreliant.think-freely.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 From: Matthew Hall Date: Thu, 30 Oct 2014 07:56:32 -0700 To: Neil Horman Message-ID: Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 14:47:52 -0000 Yes. I once had to write a cron job in Perl that monitored for unused regions and deleted them before the SHM subsystem ran out of memory. Possible, yes, but irritating. -- Sent from my mobile device. On October 30, 2014 3:18:56 AM PDT, Neil Horman wrote: >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.