| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
> I have reread the first mail in this series - I would say that Bug#2 is much > worse than Bug#1. This since Bug#1 is "only" a performance problem, > but Bug#2 is about correctness... > > Are you 100% sure that tux works with rmap? Of course not. How can I be sure??? > I would suggest testing the simplest possible case. > * Standard kernel > * concurrent dd:s Won't work. Then all I get is (ref prob #1) good throughput until RAMx2 bytes is read from disk. Then it all falls down to ~1MB/s. See http://karlsbakk.net/dev/kernel/vm-fsckup.txt for more details. > What can your problem be: > * something to do with the VM - but the problem is in several different VMs... > * something to do with read ahead? you got some patch suggestions - > please use them on a standard kernel, not rmap (for now...) Then fix the problem rmap11c fixed. I first need that fixed before being able to do any further testing! roy -- Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA Computers are like air conditioners. They stop working when you open Windows.
[Older Fedora Users Mail] [Home] [Fedora Legacy] [Fedora Desktop] [iPod Nano] [ATA RAID] [Fedora Bible] [Fedora Marketing] [Fedora Mentors] [Fedora Packaging] [Fedora SELinux] [Big List of Linux Books] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools] [Fedora Docs]
