From: Razvan Cojocaru <rzvncj@gmail.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Multiple-page mem_event ring buffer?
Date: Tue, 05 Mar 2013 16:34:12 +0200 [thread overview]
Message-ID: <51360264.3070004@gmail.com> (raw)
In-Reply-To: <20130305142140.GH2589@phenom.dumpdata.com>
>> Could I safely use more than one page for the ring buffer (passing
>> '2' as the last parameter of xc_map_foreign_batch(), and so on), or
>> am I limited to 1 page by design?
>
> You should be able to as many as you want. Are you hitting any
> particular issues?
Haven't tried it yet, I've just noticed that all the example code using
it hardcoded '1' as the number of pages it asks for, xenaccess.c has a
comment to the effect of "/* Map the ring _page_ */", and so on.
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2013-03-05 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 13:21 Multiple-page mem_event ring buffer? Razvan Cojocaru
2013-03-05 14:21 ` Konrad Rzeszutek Wilk
2013-03-05 14:34 ` Razvan Cojocaru [this message]
2013-03-05 15:00 ` Razvan Cojocaru
[not found] <mailman.25393.1362491391.1399.xen-devel@lists.xen.org>
2013-03-05 15:25 ` Andres Lagar-Cavilla
2013-03-05 15:35 ` Razvan Cojocaru
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=51360264.3070004@gmail.com \
--to=rzvncj@gmail.com \
--cc=xen-devel@lists.xen.org \
/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.