>>> On 31.03.16 at 23:26, <kon...@darnok.org> wrote: >> Also - how well will this O(n^2) lookup work once there are enough >> payloads? I think this calls for the alternative vmap() extension I've >> been suggesting earlier. > > Could you elaborate on the vmap extension a bit please? > > Your earlier email seems to say: drop the vmap API and just > allocate the underlaying pages yourself.
Actually I had also said in that earlier mail: "If, otoh, you left that VA management to (an extended version of) vmap(), by e.g. allowing the caller to request allocation from a different VA range (much like iirc x86-64 Linux handles its modules address range allocation), things would be different. After all the VA management is the important part here, while the backing memory allocation is just a trivial auxiliary operation." I.e. elaboration here really just consists of the referral to the respective Linux approach. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel