From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Keir Fraser <keir@xen.org>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2 2/2] xen/evtchn: optimize XSM ssid field
Date: Mon, 24 Mar 2014 10:53:22 +0000 [thread overview]
Message-ID: <53300EA2.5000901@citrix.com> (raw)
In-Reply-To: <532FFCFF0200007800001301@nat28.tlf.novell.com>
On 24/03/14 08:38, Jan Beulich wrote:
>
> While looking at this I started to wonder if the 100k event channel
> promise in 4.4 isn't broken: All the *_port fields here are 16-bit only,
> and hence only good for around 64k ports. If they all got widened to
> 32 bits, the structure (with the improvements above) would become
> 24/28/32 bytes. Widening them without any other adjustments
> (thinking of a backport thereof to the 4.4 branch) would appear to
> retain the current size.
Oops. We did test binding the full number of event channels but we
obviously didn't test that they actually worked properly.
David
next prev parent reply other threads:[~2014-03-24 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 15:29 [PATCH v2 1/2] xen/xsm: Reduce compiler command line clutter Daniel De Graaf
2014-03-20 15:29 ` [PATCH v2 2/2] xen/evtchn: optimize XSM ssid field Daniel De Graaf
2014-03-20 15:59 ` Jan Beulich
2014-03-21 13:28 ` David Vrabel
2014-03-21 14:54 ` Daniel De Graaf
2014-03-21 15:00 ` Jan Beulich
2014-03-21 15:16 ` David Vrabel
2014-03-21 17:43 ` Daniel De Graaf
2014-03-24 8:38 ` Jan Beulich
2014-03-24 10:53 ` David Vrabel [this message]
2014-03-24 9:07 ` Keir Fraser
2014-03-20 15:54 ` [PATCH v2 1/2] xen/xsm: Reduce compiler command line clutter Jan Beulich
2014-03-24 9:05 ` Keir Fraser
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=53300EA2.5000901@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir@xen.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).