Heinz Mauelshagen <mauelshagen@xxxxxxxxxx> wrote: >> But given the rough scenario above there *are* page-outs first. > No, a write before another read will happen unless you > found an unknown bogus case ;) Well, taking your rough scenario again, assigning it to a swap case (although it should be the same with a mmap()ing DBMS)... o page gets dirtied ...probably lots of activity... o page gets pro-actively synched to swap - handed to mirroring driver o mirroring driver initiates writes to all mirrors o write gets through to first mirror o page content gets changed (page is still dirty) o second write gets through to other mirror, page gets cleaned ...probably lots of activity... o low on physical memory, clean page gets re-mapped somewhere else ...probably lots of activity... o access to the virtual memory page that is now not mapped anymore (the one that was previously mapped to our now re-mapped page) o new mapping is created o page content is read from swap - handed to mirroring driver o mirroring driver initiates read to the first mirror o page contains content before the last change Okay, the scenario is probably bogus in the way that the access pattern is quite special: 1. you need an access pattern where a page is accessed very seldom (so it constantly runs out of the working set) 2. the race condition with the paging strategy needs to occur while one of these seldom accesses (especially while a page modify) regards Mario -- Ho ho ho! I am Santa Claus of Borg. Nice assimilation all together! - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
