lkml.org 
[lkml]   [2007]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: controlling mmap()'d vs read/write() pages
    Eric W. Biederman wrote:
    > Dave Hansen <hansendc@us.ibm.com> writes:
    >
    >
    >>So, I think we have a difference of opinion. I think it's _all_ about
    >>memory pressure, and you think it is _not_ about accounting for memory
    >>pressure. :) Perhaps we mean different things, but we appear to
    >>disagree greatly on the surface.
    >
    >
    > I think it is about preventing a badly behaved container from having a
    > significant effect on the rest of the system, and in particular other
    > containers on the system.

    That's Dave's point, I believe. Limiting mapped memory may be
    mostly OK for well behaved applications, but it doesn't do anything
    to stop bad ones from effectively DoSing the system or ruining any
    guarantees you might proclaim (not that hard guarantees are always
    possible without using virtualisation anyway).

    This is why I'm surprised at efforts that go to such great lengths
    to get accounting "just right" (but only for mmaped memory). You
    may as well not even bother, IMO.

    Give me an RSS limit big enough to run a couple of system calls and
    a loop...

    --
    SUSE Labs, Novell Inc.
    Send instant messages to your online friends http://au.messenger.yahoo.com

    -
    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/

    \
     
     \ /
      Last update: 2007-03-23 07:01    [W:4.268 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site