> Hi Michael.
>
> > This I believe is a known problem which is being addressed by the
> > vm magicians. It will get better when someone figures out how to
> > solve the fragmentation issues.. and no sooner I think.
>
> Here's a summary of what's been reported so far...
>
> 1. Two drives, one partition on each, both pri=1, thrash badly.
> (Original report).
>
My setup is two partitions at same priority on seperate drives, and
I have no thrashing.
> This does suggest a possible set of rules, but more reports are needed
> to verify them. The rule-set suggested is as follows:
>
> 1. TWO OR MORE swap partitions.
>
> 2. TWO OR MORE of these SHARE the HIGHEST priority level.
>
Mine are both at highest.
> 3. The ones that share the highest priority level are on DIFFERENT
> drives, with not more than one on each drive involved.
That matches my setup.
>
> To ocomplete the picture, I'd like to receive further reports, and
> ESPECIALLY for either of the following conditions:
>
> A. Thrashing NOT occurring when the above conditions are met.
> Please state your partition setup.
/dev/sda1 * 1 1 201 205808 6 DOS 16-bit >=32M
/dev/sda2 202 202 802 615424 6 DOS 16-bit >=32M
/dev/sda3 803 803 1003 205824 83 Linux native
/dev/sdb1 1 1 70 71664 83 Linux native
/dev/sdb2 71 71 100 30720 83 Linux native
/dev/sdb3 101 101 1886 1828864 83 Linux native
/dev/sdb4 1024 1887 2014 131072 82 Linux swap
/dev/sdc1 1 1 1885 1930224 83 Linux native
/dev/sdc2 1024 1886 2014 132096 82 Linux swap
/dev/sdd1 1 1 65 66544 83 Linux native
/dev/sdd2 66 66 1750 1725440 83 Linux native
/dev/sdd3 1024 1751 1879 132096 83 Linux native
[root]:# swapon -s
Filename Type Size Used Priority
/dev/sdb4 partition 130748 0 1
/dev/sdc2 partition 130748 0 1
I suspect that the thrashing is low mem/high fragmentation related.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu