On Mon, Aug 5, 2013 at 11:24 AM, Dave Hansen <dave.hansen@xxxxxxxxx> wrote: > On 08/05/2013 11:04 AM, Luigi Semenzato wrote: >> We can reproduce this by running a few processes that mmap large >> chunks of memory, then randomly touch pages to fault them in. We also >> think this happens when a process writes a large amount of data using >> buffered I/O, and the "Buffers" field in /proc/meminfo exceeds 1GB. >> (This is something that can and should be corrected by using >> unbuffered I/O instead, but it's a data point.) > > Where are all the buffers coming from? Most I/O to/from filesystems > should be instantiating relatively modest amounts of Buffers. Are you > doing I/O directly to devices for some reason? Correct. This is the autoupdate process, which writes the changed kernel and filesystem blocks directly to raw partitions. (The filesystem partition is obviously not currently in use.) -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>