[merge] readv out of order

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> Since I've been looking into the readv() stuff for http, I went ahead
> and looked closer into it for other transports.
> 
> It turns out that rather frequently we actually try to readv() out of
> order. One place where this happens a lot is when combining the
> signature.knit. I think we are trying to read in ancestry order, which
> signature.knit definitely doesn't follow.
> 
> But I think it also happens when we are reading other files, and they
> aren't in 'merge_sort' topological sorted order. They are probably in
> some sort of topological order, but not the one we are looking for.
> 

I just wanted to mention that this patch isn't 100% ready for merging.
I'm doing some automated performance tests (that are going to take about
30hrs to finish). And still need to do some cleanups. But I thought I
would let people know how it was going so far.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEuTmUJdeBCYSNAAMRAvgSAJ9QfhnTXqXX0Q9eeZC1k4I8S3wSgACgkAdo
WFsYTeEfDV/AI+kIWzv2gjY=
=JmQp
-----END PGP SIGNATURE-----