From: Nivedita Singhvi <niv@us.ibm.com>
To: James Dykman <dykman@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] [XM-TEST] Use explicit (IP id==packet size) on hping2 tests to avoid problems with IP id==0
Date: Thu, 18 May 2006 15:42:59 -0700 [thread overview]
Message-ID: <446CF873.6020207@us.ibm.com> (raw)
In-Reply-To: <OF5F3D4DA4.0866EA33-ON85257172.0076DC9C-85257172.007862C1@us.ibm.com>
James Dykman wrote:
>>Jim, will this not be a cause potential corruption - if we have incoming
>>fragments belonging to different packets with the same ipid
>>there is no way for the reassembly code to distinguish them.
>>Checksum failures might catch some, but that is no guarantee of
>>safe delivery.
>>
>
>
> That possibility exists in the tests as they are today... hping2 is
> assigning IP ids based on
> its PID, completely independent of the kernel.
1. This might be fine for temporary purposes (although
we send multiple packets of the same size in consecutive
order, so only serialization is helping us in those
tests, correct? Perhaps something that would be unique
at least across the xmtest set of hpings for sure?)
> If you want to solve that problem TOO, then we need to replace hping2. Any
> suggestions?
How about for now removing the hping tests which involve
sends of > MTU size, and using ping and netperf udp/tcp tests
to replace those (underway)?
This is just to avoid another round of bugs further down
the road when we get to SMP testing in a serious way.
thanks,
Nivedita
prev parent reply other threads:[~2006-05-18 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 20:04 [PATCH] [XM-TEST] Use explicit (IP id==packet size) on hping2 tests to avoid problems with IP id==0 James Dykman
2006-05-18 21:32 ` Nivedita Singhvi
2006-05-18 21:54 ` James Dykman
2006-05-18 22:42 ` Nivedita Singhvi [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=446CF873.6020207@us.ibm.com \
--to=niv@us.ibm.com \
--cc=dykman@us.ibm.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.