On Wed, Jul 08, 2015 at 04:32:36PM +0200, Samuel Thibault wrote:
> > Isn't a per-process limit rather pointless?  I thought Linux limit is
> > per-user.
> 
> On Linux it's per process too, changing ulimit -l in a process won't
> affect another process.
> 
> The issue with mlocked memory is mostly about eating non-pageable
> memory. Creating processes already eats non-pageable memory anyway, so
> it doesn't buy much to eat a bit more non-pageable memory per process.

The rationale is that you restrict the number of processes per user
instead, so it's fine.

> > Oh, and why did you chose `mach4.defs' to add a new RPC?  I mean, it
> > doesn't really matter, the Mach API isn't properly grouped into
> > protocols, and there is just one huge dispatcher, but I thought we put
> > new definitions into `gnumach.defs'.
> 
> I don't really know actually. I'd tend to think that mach4.defs is for
> newer RPCs which make sense on oldish Mach, while gnumach.defs is for
> GNU-introduced features, but I really don't know the rules.

At this point, we make the rules, and it was decided we would put our
own RPCs in gnumach.defs. The mach4.defs file is really meant to contain
stuff that came with Mach 4.

-- 
Richard Braun

Reply via email to