qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Wiesinger <lists@wiesinger.com>
To: Yan Vugenfirer <yan@daynix.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Alex Fishman <alex.fishman@ravellosystems.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Tamir Shomer <tamirs@daynix.com>,
	yvugenfi@redhat.com, Izik Eidus <izik.eidus@ravellosystems.com>,
	qemu-devel@nongnu.org, Dmitry Fleytman <dmitry@daynix.com>
Subject: Re: [Qemu-devel] [PATCH 7/7 v5] VMXNET3 paravirtualized device implementation Interface type "vmxnet3" added.
Date: Thu, 5 Apr 2012 21:00:18 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1204051949550.31949@bbs.intern> (raw)
In-Reply-To: <CALBs2cXGERTvZkw+4kWiMD+Qjc8VyHo27uMhDq1KcryXiEW2aw@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1687 bytes --]

On Thu, 5 Apr 2012, Yan Vugenfirer wrote:

> On Thu, Apr 5, 2012 at 8:25 AM, Gerhard Wiesinger <lists@wiesinger.com> wrote:
>>
>> On Wed, 4 Apr 2012, Izik Eidus wrote:
>>>
>>> What about this patch?, everything that was asked from Dmitry was accomplished...
>>> What prevent us from progressing with merging this patch?
>>
>>
>> As already discussed on the list patch v5 doesn't work at least for me. Previous patches worked better but were not stable under load.
>>
>> I'm also appreciating a working version and integrating the patch fast.
>>
>> Ciao,
>> Gerhard
>>
>> --
>> http://www.wiesinger.com/
>
> Hello Gerhard,
>
> 1. I understand that you send your exact command line to Dmitry and
> your test scripts, but we cannot reproduce the issues. Can you send us
> host network configuration?
>
> 2. Is it possible for you to run tcpdump on the guest and on the host
> and send us the files for review?

Since there was no difference for v5 patch, I already sent this for v4 
patch:

See:
https://lists.gnu.org/archive/html/qemu-devel/2012-03/msg04062.html
https://lists.gnu.org/archive/html/qemu-devel/2012-03/msg04634.html

I also sniffed between working NIC (rtl8139) and non working
NIC (vmxnet3) and as already thought in
//lists.gnu.org/archive/html/qemu-devel/2012-03/msg04062.html
TCP offloading checksum is NOT correct.

>From wireshark sniff:
Checksum SYN1: 0xe937 [incorrect, should be 0xe936 (maybe caused by "TCP checksum offload"?)]
Checksum SYN2: [incorrect, should be 0xe5af (maybe caused by "TCP checksum offload"?)]
=> checksum is always too high by 1.

Please fix it.

Ciao,
Gerhard

--
http://www.wiesinger.com/

      reply	other threads:[~2012-04-05 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18  9:26 [Qemu-devel] [PATCH 0/7 v5] VMXNET3 paravirtual NIC device implementation Dmitry Fleytman
2012-03-18  9:26 ` [Qemu-devel] [PATCH 1/7 v5] Adding missing flag VIRTIO_NET_HDR_F_DATA_VALID from Linux kernel source tre Reformatting comments according to checkpatch.pl requirements Dmitry Fleytman
2012-03-18  9:26 ` [Qemu-devel] [PATCH 2/7 v5] Adding utility function net_checksum_add_cont() that allows checksum calculation of scattered data with odd chunk sizes Dmitry Fleytman
2012-03-18  9:26 ` [Qemu-devel] [PATCH 3/7 v5] Adding utility function iov_net_csum_add() for iovec checksum calculation Dmitry Fleytman
2012-03-18  9:26 ` [Qemu-devel] [PATCH 4/7 v5] Header with various utility functions shared by VMWARE SCSI and network devices Dmitry Fleytman
2012-03-18  9:27 ` [Qemu-devel] [PATCH 5/7 v5] Various utility functions used by VMWARE " Dmitry Fleytman
2012-03-18  9:27 ` [Qemu-devel] [PATCH 6/7 v5] Packet abstraction " Dmitry Fleytman
2012-03-18  9:27 ` [Qemu-devel] [PATCH 7/7 v5] VMXNET3 paravirtualized device implementation Interface type "vmxnet3" added Dmitry Fleytman
2012-04-04 11:44   ` Izik Eidus
2012-04-04 19:39     ` Michael S. Tsirkin
2012-04-05  5:25     ` Gerhard Wiesinger
2012-04-05  8:02       ` Yan Vugenfirer
2012-04-05 19:00         ` Gerhard Wiesinger [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=alpine.LFD.2.02.1204051949550.31949@bbs.intern \
    --to=lists@wiesinger.com \
    --cc=alex.fishman@ravellosystems.com \
    --cc=aliguori@us.ibm.com \
    --cc=dmitry@daynix.com \
    --cc=izik.eidus@ravellosystems.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tamirs@daynix.com \
    --cc=yan@daynix.com \
    --cc=yvugenfi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).