Date: Fri, 12 Oct 2012 20:55:28 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Tim LaBerge <tlaberge@juniper.net>, "freebsd-arch@freebsd.org Arch" <freebsd-arch@freebsd.org>, Alan Cox <alc@rice.edu> Subject: Re: Behavior of madvise(MADV_FREE) Message-ID: <6068.1350075328@critter.freebsd.dk> In-Reply-To: <E6A52D27-0D6A-4175-9ECA-ADE25BFF35C2@xcllnt.net> References: <9FEBC10C-C453-41BE-8829-34E830585E90@xcllnt.net> <4835.1350062021@critter.freebsd.dk> <E6A52D27-0D6A-4175-9ECA-ADE25BFF35C2@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <E6A52D27-0D6A-4175-9ECA-ADE25BFF35C2@xcllnt.net>, Marcel Moolenaar writes: >BTW: MADV_DONTNEED in Linux seems to behave like MADV_FREE >in FreeBSD -- at least according to the manpage. Which makes >me wonder how standard madvise(2) is anyway. "Not at all" is how much standard it is. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6068.1350075328>