All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Reese Faucette" <reese@myri.com>
To: xen-devel@lists.xensource.com
Subject: Re: vif interface dropping 80% packets
Date: Tue, 6 Feb 2007 15:35:30 -0800	[thread overview]
Message-ID: <00cd01c74a47$7d915b40$58c31fac@bart> (raw)
In-Reply-To: 8A87A9A84C201449A0C56B728ACF491E04F46E@liverpoolst.ad.cl.cam.ac.uk

>> update:
>> The performance is better with 9k MTU, as expected:
>> TCP_STREAM and TCP_SENDFILE both get ~1.8Gb/s, xentop reports 87%
>> utilization for dom0, so I guess that's about all I can expect without
>> code changes.
>
> I've seen rather better figures than this with another 10G card.
> Does your NIC/driver support TSO and LRO?

yes to both, and have tried with LRO both enabled and disabled.  again, the 
dom0 performance is fine, it's just to domU that is slower.  I have network 
bridging set up on this interface, i.e. peth2, eth2, xenbr2, etc. - is that 
not the way I should be doing it?

>> 2) if yes, Will the patch "fedora-36252.patch" work on the 2.6.16
>> kernel included with 3.0.4, or have conflicts crept in?
>
> No idea. What does the patch do?

This was the mythical patch to make 2.6.18 into a Xen-aware kernel.  Took me 
forever to track it down - is there a more obvious place to look?  Sorry to 
just refer to the file by name, after googling forever i decided i was the 
only person in the Xen world not intimately familiar with this patch.
-reese

  reply	other threads:[~2007-02-06 23:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06  0:30 vif interface dropping 80% packets Reese Faucette
2007-02-06  2:33 ` Reese Faucette
2007-02-06 13:43 ` Ian Pratt
2007-02-06 18:12 ` Santos, Jose Renato G
2007-02-06 18:58   ` Reese Faucette
2007-02-06 19:40     ` Santos, Jose Renato G
2007-02-06 22:52       ` Reese Faucette
2007-02-06 23:06         ` Ian Pratt
2007-02-06 23:35           ` Reese Faucette [this message]
2007-02-06 23:59             ` Ian Pratt
2007-02-07 20:52               ` Reese Faucette
2007-02-07 22:28                 ` Ian Pratt
2007-02-07  0:16             ` Santos, Jose Renato G

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='00cd01c74a47$7d915b40$58c31fac@bart' \
    --to=reese@myri.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.