From: Wei Liu <Wei.Liu2@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Wei Liu <liuw@liuw.name>,
wei.liu2@citrix.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH 2/3] Dynamically allocate domain->evtchn, also bump EVTCHNS_PER_BUCKET to 512.
Date: Wed, 2 Jan 2013 14:27:42 +0000 [thread overview]
Message-ID: <1357136862.8077.28.camel@iceland> (raw)
In-Reply-To: <50E43851.4080502@citrix.com>
On Wed, 2013-01-02 at 13:38 +0000, David Vrabel wrote:
> On 31/12/12 18:22, Wei Liu wrote:
> > From: Wei Liu <liuw@liuw.name>
>
> The changeset description needs to say why you're increasing
> EVTCHNS_PER_BUCKET. I can't tell why.
>
Here is the tedious maths. My thought was that it is not very
interesting to see this in a change log, so I dropped it. But I will add
this in my later re-post of this series...
#define EVTCHNS_PER_BUCKET ???
#define NR_EVTCHN_BUCKETS (NR_EVENT_CHANNEL_L3/EVTCHNS_PER_BUCKET)
d->evtchn = xzalloc_array(struct evtchn *, NR_EVTCHN_BUCKETS);
We need to allow for 3-level evtchn, so use NR_EVENT_CHANNELS_L3 to
calculate NR_EVTCHN_BUCKETS.
For 64 bit build, NR_EVENT_CHANNELS_L3 is 256k. The original value of
EVTCHNS_PER_BUCKET is 128, which means NR_EVTCHN_BUCKETS=2048, thus
d->evtchn has size of 2048*8 = 16KB = 4 pages. Given that only Dom0 or
driver domain will need 3-level event channel, this is really overkill
for most guests.
If we bump EVTCHNS_PER_BUCKET to 512, d->evtchn becomes 512 * 8 = 4KB =
1 page, which I think is more space efficient for most guests.
Of course, bumping EVTCHNS_PER_BUCKETS will cause overhead in other
place. Xen allocates a buckets-size of struct evtchn at a time. So the
overhead is:
sizeof(struct evtchn) * (512-128) ~= 18 bytes * 384
So the conclusion is:
1 page + sizeof(struct evtchn) * 384 < 4 pages
IMHO this is a good reason to bump EVTCHNS_PER_BUCKETS to 512.
Wei.
> > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> > ---
> > xen/common/event_channel.c | 8 ++++++++
> > xen/include/xen/sched.h | 4 ++--
> > 2 files changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
> > index 87e422e..9898f8e 100644
> > --- a/xen/common/event_channel.c
> > +++ b/xen/common/event_channel.c
> > @@ -1172,6 +1172,12 @@ void notify_via_xen_event_channel(struct domain *ld, int lport)
> >
> > int evtchn_init(struct domain *d)
> > {
> > + d->evtchn = (struct evtchn **)
> > + xzalloc_array(struct evtchn *, NR_EVTCHN_BUCKETS);
>
> Don't need the cast here?
>
> David
next prev parent reply other threads:[~2013-01-02 14:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 18:22 Implement 3-level event channels in Xen Wei Liu
2012-12-31 18:22 ` [RFC PATCH 1/3] Add a field in struct domain to indicate evtchn level Wei Liu
2013-01-02 11:11 ` David Vrabel
2013-01-02 14:28 ` Wei Liu
2012-12-31 18:22 ` [RFC PATCH 2/3] Dynamically allocate domain->evtchn, also bump EVTCHNS_PER_BUCKET to 512 Wei Liu
2013-01-02 13:38 ` David Vrabel
2013-01-02 14:27 ` Wei Liu [this message]
2013-01-03 10:36 ` Jan Beulich
2013-01-03 11:33 ` Wei Liu
2013-01-03 11:39 ` Jan Beulich
2012-12-31 18:22 ` [RFC PATCH 3/3] Implement 3-level event channel routines Wei Liu
2013-01-02 14:08 ` David Vrabel
2013-01-02 16:45 ` Ian Campbell
2013-01-03 10:46 ` Jan Beulich
2013-01-03 11:35 ` Jan Beulich
2013-01-08 17:33 ` Wei Liu
2013-01-09 8:38 ` Jan Beulich
2013-01-09 10:56 ` Ian Campbell
2013-01-09 11:24 ` Jan Beulich
2013-01-09 11:31 ` Ian Campbell
2013-01-09 11:41 ` Jan Beulich
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=1357136862.8077.28.camel@iceland \
--to=wei.liu2@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=liuw@liuw.name \
--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.