All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Cc: stse+xen@fsing.rootsland.net, Adnan Misherfi <adnan.misherfi@oracle.com>
Subject: Re: Re: Jeremy's GIT-tree and network problems
Date: Tue, 30 Mar 2010 10:30:06 -0400	[thread overview]
Message-ID: <20100330143006.GD10728@phenom.dumpdata.com> (raw)
In-Reply-To: <20100330T1423.GA.57721.stse@fsing.rootsland.net>

On Tue, Mar 30, 2010 at 02:26:00PM +0200, Stephan Seitz wrote:
> On Mon, Mar 29, 2010 at 08:18:15PM +0200, S.H. Verbrugge wrote:
>> Could you check your dmesg (dom0) to see if you have similar messages?
>> http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00966.html
>
> You mean „Attempting to checksum a non-TCP/UDP packet, dropping a 
> protocol 1 packet”? Yes, I see one shortly before the NFSv4 server is  
> started. But it is only one line and doesn’t show again if I start my  
> connection tests.


So here is an interesting observation (And I am late in this thread so
if I am going off on a tangent, please correct me): We compiled both in
DomU and Dom0 the kernel to not have any traces of iptables nor
igbtables. The performance of scp-ing a tarball from Dom0 to DomU went
from 0.5MB to 17MB/s (which is about the disk speed).

I don't know if you feel inclined to actually try such a drastic option
to see if that is your culprit or not, but it is worth keeping in the
back of your head.

  reply	other threads:[~2010-03-30 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 15:40 Jeremy's GIT-tree and network problems Stephan Seitz
2010-03-29 18:18 ` S.H. Verbrugge
2010-03-30 12:26   ` Stephan Seitz
2010-03-30 14:30     ` Konrad Rzeszutek Wilk [this message]
2010-03-30 19:39       ` Stephan Seitz
2010-03-29 18:42 ` Jeremy Fitzhardinge
2010-03-30 12:33   ` Stephan Seitz
2010-05-03 18:48   ` Stephan Seitz

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=20100330143006.GD10728@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=adnan.misherfi@oracle.com \
    --cc=stse+xen@fsing.rootsland.net \
    --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.