All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jambunathan K <jambunathan@netxen.com>
To: xen-devel@lists.xensource.com
Cc: Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: PCI Passthrough & iperf Throughput Skew
Date: Tue, 27 Mar 2007 20:10:17 +0530	[thread overview]
Message-ID: <46092CD1.3090903@netxen.com> (raw)
In-Reply-To: <46092BBA.6000105@netxen.com>

Additional Data Point:

If I just exercise iperf in Dom0 or DomU *separately*, I get identical
throughput .  The 10:1 skew happens only when the iperf is running
concurrently on the Dom0 and DomU.

Regards,
Jambunathan K.

Jambunathan K wrote:
> I am seeing a strange behaviour with Xen-3.0.4 which seems to suggest
> that Dom0 has either higher Scheduling affinity or Interrupt affinity.
>
> I am in the initial stages of investigation and it is possible that my
> hunch is totally wrong. I would like to hear comments or questions
> from the experts.
>
> I have a multifunction NIC card, with one function being used by Dom0
> and another one exported to DomU using PCI passthrough
>
> Dom0 and DomU have almost the same memory allocated to each
> (~1.3G). The ports themselves are operating at the same speed and
> share the same IRQ.
>
> iperf (as a client) is started on Dom0 in the same way as it is
> started on DomU.
>
> iperf results are skewed in favour of Dom0 in the ratio 10:1.
>
> Given all other things are similar wouldn't it be normal to expect
> throughputs in the ratio of 1:1.
>
> (ps:- The 2 ports on the Xen machine is connected
> "point-to-point-wise" to 2 ports on another machine running Linux
> natively)
>
>
> Regards,
> Jambunathan K.
>
>
>
>
>
>
>
>

      reply	other threads:[~2007-03-27 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 14:35 PCI Passthrough & iperf Throughput Skew Jambunathan K
2007-03-27 14:40 ` Jambunathan K [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=46092CD1.3090903@netxen.com \
    --to=jambunathan@netxen.com \
    --cc=sanjeev@netxen.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.