From: Pat Campbell <plc@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Derek Murray <Derek.Murray@cl.cam.ac.uk>,
Xen Development Mailing List <xen-devel@lists.xensource.com>,
Markus Armbruster <armbru@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: Re: userspace block backend / gntdev problems
Date: Sun, 27 Jan 2008 17:40:03 -0700 [thread overview]
Message-ID: <479D2463.8060509@novell.com> (raw)
In-Reply-To: <C3C0A454.12DE7%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 26/1/08 08:41, "Markus Armbruster" <armbru@redhat.com> wrote:
>
>
>>> In my latest post on "Dynamic modes support for PV xenfb" I am using
>>> grants to map an extended framebuffer. I have a single grant ref that
>>> points to 10 other refs. The other refs contain MFNs. Same technique as
>>> the current framebuffer pd array but avoids the 64bit long issue. Kind
>>> of a hybrid approach. I am able to map a 22MB framebuffer when running a
>>> 64 bit guest and 44MB when running a 32 bit guest. When the backend is
>>> done with the mapping it sends a message to the frontend to free up the
>>> refs.
>>>
>> Uhm, I fear I didn't get the advantage of your hybrid approach. Could
>> you explain?
>>
>
> Presumably it allows creation of huge framebuffers without using up lots of
> grants, or slots in accounting tables that Xen maintains. Given that those
> tables can dynamically grow, I'm not sure how useful the two-level grant
> table would be.
>
> -- Keir
>
>
>
Well, turns out my email did not really get sent. Keir is right, it is
a two level grant table. Solution might not be useful in the general
case but for this device I think it fits the bill. Existing xenfb code
is already doing a two level table which has to be maintained for
backward compatibility reasons, might as well be consistent. Also by
using a two level grant table we don't have to extend the event
structure which might be a compatibility issue.
I will get my patches sent up for your review directly.
Pat
prev parent reply other threads:[~2008-01-28 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 13:48 userspace block backend / gntdev problems Gerd Hoffmann
2008-01-04 14:50 ` Derek Murray
2008-01-04 15:24 ` Gerd Hoffmann
2008-01-21 18:41 ` Markus Armbruster
2008-01-25 23:29 ` Pat Campbell
2008-01-26 8:41 ` Markus Armbruster
2008-01-26 8:48 ` Keir Fraser
2008-01-28 0:40 ` Pat Campbell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=479D2463.8060509@novell.com \
--to=plc@novell.com \
--cc=Derek.Murray@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.