From: Diwaker Gupta <diwakergupta@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: I/O descriptor ring size bottleneck?
Date: Sun, 20 Mar 2005 16:06:38 -0800 [thread overview]
Message-ID: <1b0b455705032016066e62d3b8@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3771@liverpoolst.ad.cl.cam.ac.uk>
> BTW, I'd actually be very suspicious of dummynet's ability to operate at
> 500Mb/s. It's possible that the reduced bandwidth is due to some bad
> interaction between burstiness caused by Xen's context switching and
> dummynet.
Could you elaborate a bit more on this? Even if dummynet can't operate
at 500Mbps, we should atleast see the same degradation in performance
right?
> Are your dom0 and domU running on the same processor? Could you try
> using hyperthreading or SMP?
Yep, same processor. For various other reasons, I wanted to avoid SMP,
so I was running with the nosmp option. I'll try running with SMP and
post an update.
> Have you checked that domU <-> domU performance is good on the LAN with
> a single TCP connection?
I had a long time back, but I think that was with SMP. I'll check again.
--
Diwaker Gupta
http://resolute.ucsd.edu/diwaker
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-21 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 22:15 I/O descriptor ring size bottleneck? Ian Pratt
2005-03-21 0:06 ` Diwaker Gupta [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-21 0:36 Ian Pratt
2005-03-20 21:47 Diwaker Gupta
2005-03-21 23:42 ` Nivedita Singhvi
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=1b0b455705032016066e62d3b8@mail.gmail.com \
--to=diwakergupta@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.