Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Feb 2013 19:25:47 -0800
From:      John-Mark Gurney <jmg@funkthat.com>
To:        Ben Morrow <ben@morrow.me.uk>
Cc:        jdc@koitsu.org, freebsd-stable@freebsd.org
Subject:   Re: svn - but smaller?
Message-ID:  <20130225032546.GL55866@funkthat.com>
In-Reply-To: <20130225002847.GA42160@anubis.morrow.me.uk>
References:  <web-10502111@mailback3.g2host.com> <web-12014638@mailback4.g2host.com> <op.wszomvfyg7njmm@michael-think> <20130224031509.GA47838@icarus.home.lan> <op.wszrv9k5g7njmm@michael-think> <20130224041638.GA51493@icarus.home.lan> <op.wszt3wh2g7njmm@michael-think> <20130224063110.GA53348@icarus.home.lan> <1361726397.16937.4.camel@revolution.hippie.lan> <20130225002847.GA42160@anubis.morrow.me.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
Ben Morrow wrote this message on Mon, Feb 25, 2013 at 00:28 +0000:
> > 1. Such buffers exist during the entire program's lifetime even if they
> > aren't actively used/needed by the program.  With malloc(3) and friends,
> > you're allocating memory dynamically, and you can free(3) when done with
> > it, rather than just having a gigantic portion of memory allocated
> > sitting around potentially doing nothing.
> 
> If the 'allocated' memory isn't touched, it will never be paged in. Even
> once it is paged in, if it then goes back to being unused it can be
> paged out to swap (when necessary) and then stay there. (It would be
> nice if there were some way to tell the system 'this memory is dead,
> don't write it out to swap', but I don't think there is.)

madvise(2) w/ MADV_FREE, though there was some discussion on -current
about what these different flags will/should do not too long ago...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130225032546.GL55866>