From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754176Ab2AXPxM (ORCPT ); Tue, 24 Jan 2012 10:53:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40175 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752166Ab2AXPxJ (ORCPT ); Tue, 24 Jan 2012 10:53:09 -0500 Date: Tue, 24 Jan 2012 13:40:01 -0200 From: Marcelo Tosatti To: Pekka Enberg Cc: Rik van Riel , Minchan Kim , linux-mm , LKML , leonid.moiseichuk@nokia.com, kamezawa.hiroyu@jp.fujitsu.com, mel@csn.ul.ie, rientjes@google.com, KOSAKI Motohiro , Johannes Weiner , Andrew Morton , Ronen Hod , KOSAKI Motohiro Subject: Re: [RFC 1/3] /dev/low_mem_notify Message-ID: <20120124154001.GB10990@amt.cnet> References: <1326788038-29141-1-git-send-email-minchan@kernel.org> <1326788038-29141-2-git-send-email-minchan@kernel.org> <4F15A34F.40808@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 17, 2012 at 08:51:13PM +0200, Pekka Enberg wrote: > Hello, > > Ok, so here's a proof of concept patch that implements sample-base > per-process free threshold VM event watching using perf-like syscall > ABI. I'd really like to see something like this that's much more > extensible and clean than the /dev based ABIs that people have > proposed so far. > > Pekka What is the practical advantage of a syscall, again?