Date: Thu, 13 Jun 2013 10:43:47 -0400
From: =?utf-8?B?SsO2cm4=?= Engel <joern@logfs.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RFC] mm: Implement RLIMIT_RSS
Message-ID: <20130613144347.GA13217@logfs.org>
References: <20130611182921.GB25941@logfs.org>
 <20130611211601.GA29426@cmpxchg.org>
 <20130611215319.GA29368@logfs.org>
 <20130613085732.GB4533@bbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20130613085732.GB4533@bbox>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 838
Lines: 22

On Thu, 13 June 2013 17:57:32 +0900, Minchan Kim wrote:
> 
> It means you already know the max rss of the application in advance
> so you can use taskstats's hiwater_rss if you don't need to catch
> the moment which rss is over the limit.

I would like to catch the very moment.  Just for my particular needs,
it doesn't matter much if you overshoot by 10% or so.  But eventually
I would like a patch that is off by less than 1% and low-overhead at
the same time.

Jörn

--
Measuring programming progress by lines of code is like measuring aircraft
building progress by weight.
-- Bill Gates
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/