lkml.org 
[lkml]   [2005]   [Jun]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: wrong madvise(MADV_DONTNEED) semantic
On Tue, Jun 28, 2005 at 03:43:16PM +0200, Samuel Thibault wrote:
> There is something wrong with the current madvise(MADV_DONTNEED)
> implementation. Both the manpage and the source code says that
> MADV_DONTNEED means that the application does not care about the data,
> so it might be thrown away by the kernel.

I agree that the Linux madvise manpage is unclear and should be fixed.

If your interpretation of the problem is correct, then it should be
trivial to write a test program demonstrating the problem. Did you
write the simple test program and run it?

I did, and the results make me think that the Linux implementation does
conform to the POSIX spec you quote. I did not observe any data loss.

So it's just a documentation issue.

Besides, if you read the documentation closely, it does not say what you
think it says.

MADV_DONTNEED
Do not expect access in the near future. (For the time
being, the application is finished with the given range,
so the kernel can free resources associated with it.)
Subsequent accesses of pages in this range will succeed,
but will result either in reloading of the memory contents
from the underlying mapped file (see mmap) or
zero-fill-on-demand pages for mappings without an
underlying file.

You seem to think that "reloading ... from the underlying mapped file"
means that changes are lost, but that's not implied.

Also, the parenthetical near the top of the manpage "(except in the case
of MADV_DONTNEED)" is, AFAICS, wrong. MADV_DONTNEED does not affect
semantics. It looks to me like someone "improved" madvise.2 without
actually understanding what they were talking about.

Below is the test program I used.

-andy

#include <stdio.h>
#include <stdlib.h>
#include <stdarg.h>
#include <string.h>
#include <errno.h>

#include <unistd.h>
#include <sys/mman.h>
#include <fcntl.h>
#include <sys/stat.h>

typedef unsigned int u32;

void die(char *fmt, ...)
{
va_list ap;
va_start(ap, fmt);
vfprintf(stderr, fmt, ap);
va_end(ap);
exit(1);
}
int check_cookie(char *file, u32 cookie)
{
u32 buf;
int fd;
if((fd = open(file, O_RDONLY, 0)) == -1)
die("%s: %s\n", file, strerror(errno));
if(read(fd, &buf, sizeof(buf)) == -1)
die("read: %s\n", strerror(errno));
close(fd);
return buf == cookie;
}
int dotest(char *file, u32 cookie, int do_msync, int do_madvise)
{
void *p;
int fd, len = 16 * 1024, prot = PROT_READ|PROT_WRITE;
if((fd = open(file, O_RDWR|O_CREAT, 0666)) == -1)
die("%s: %s\n", file, strerror(errno));
if(ftruncate(fd, len) == -1)
die("ftruncate: %s\n", strerror(errno));
if(write(fd, "", 1) == -1)
die("write: %s\n", strerror(errno));
if((p = mmap(0, len, prot, MAP_SHARED, fd, 0)) == MAP_FAILED)
die("mmap: %s\n", strerror(errno));
*(u32 *)p = cookie;

if(do_msync)
if(msync(p, len, MS_SYNC) == -1)
die("msync: %s\n", strerror(errno));
if(do_madvise)
if(madvise(p, len, MADV_DONTNEED) == -1)
die("madvise: %s\n", strerror(errno));
if(close(fd) == -1)
die("close: %s\n", strerror(errno));
printf("c = %08x msync: %s madvise: %s %s\n",
cookie, do_msync ? "YES" : " NO", do_madvise ? "YES" : " NO",
check_cookie(file, cookie) ? "ok" : "FAILED");
}

int main(int argc, char **argv)
{
if(argc != 2) die("usage: %s file\n", argv[0]);
lrand48();
dotest(argv[1], lrand48(), 0, 0);
dotest(argv[1], lrand48(), 1, 0);
dotest(argv[1], lrand48(), 0, 1);
dotest(argv[1], lrand48(), 1, 1);
}
-
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: 2005-06-28 20:20    [from the cache]
©2003-2011 Jasper Spaans