From: Niraj Tolia <ntolia@gmail.com>
To: Ian Pratt <ian.pratt@cl.cam.ac.uk>
Cc: Keir Fraser <keir.fraser@cl.cam.ac.uk>, xen-devel@lists.sourceforge.net
Subject: Re: Fwd: Dom0 OOPS - causes restart
Date: Mon, 12 Jul 2004 17:23:25 +0100 [thread overview]
Message-ID: <7e45e2ac04071209234cf9be25@mail.gmail.com> (raw)
In-Reply-To: <E1Bk3K5-00072O-00@mta1.cl.cam.ac.uk>
On Mon, 12 Jul 2004 17:06:33 +0100, Ian Pratt <ian.pratt@cl.cam.ac.uk> wrote:
> > Sorry if this email is a duplicate but that patch seems to work. Three
> > runs of Postmark completed without problems. I will let you know in
> > case anything else turns up though.
>
> While debugging this we spotted what looks like a network
> performance issue: We were only receiving 500Mb/s of TCP
> throughput into domain 1 from the LAN rather than the usual
> 895Mb/s (which is what you get for transmit; 128KB socket buffer
> size).
>
> Are you seeing any odd performance numbers?
>
Still not at the stage yet when I can start comparing. In fact, the
odds are that I might not see similar problems in my setup as my iSCSI
initiator is a hardware card (the Intel 1000 ProT) that does its own
networking outside of xen. However, I will definitely let you know if
I see something strange.
Also, if you haven't done this already and feel that it might be
useful, I can try running netperf so see what kind of bandwidth I
observe.
Niraj
> It's possible that enabling CONFIG_NETFILTER by default was a
> mistake.
>
> It's also possible that we've introduced some other more subtle
> performance bug :-(
>
> Ian
>
>
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
parent reply other threads:[~2004-07-12 16:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1Bk3K5-00072O-00@mta1.cl.cam.ac.uk>]
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=7e45e2ac04071209234cf9be25@mail.gmail.com \
--to=ntolia@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=keir.fraser@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.