Hi again. (I know from your more recent email that you already know the answer to this, but others might be interested so I'll reply anyway). On 26/09/10 01:04, Martin Steigerwald wrote: > Am Samstag 25 September 2010 schrieb Nigel Cunningham: >> Hi Rafael. > > Hi Nigel, > >> Please find attached a slightly updated version of the patchset I sent >> a few months ago. The main change is that I've prepended and additional >> patch which lets the user see the speed at which the image is being >> read and written. This is accomplished by recording the MB/s in a >> single byte in the image header, and using a couple of __nosavedata >> variables to get the data back through the atomic restore. I realise >> the char limits us to 255MB/s at the moment. In future patches, I >> intend to address this by storing the data in a 'proper' image header >> (it's a real problem - TuxOnIce reads and writes on the same set up at >> speeds around 250MB/s). > > I like to help by testing these. Is it sufficient to check out your latest > tuxonice tree, checkout branch for-rafael and switch the hibernate script > to TryMethod disk.conf? Yes, that should be sufficient. You do need to be aware (as I said in the other reply) that I'm treating this branch like a temporary branch, so it's getting rebased and having little modifications made to it. Pulling will therefore sometimes require the use of the force option. Regards, Nigel _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
