From: David Miller <davem@davemloft.net>
To: zoltan.kiss@citrix.com
Cc: steffen.klassert@secunet.com, minipli@googlemail.com,
dborkman@redhat.com, tgraf@suug.ch, joe@perches.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH net-next 0/4 v5] pktgen: Upstreaming features useful for xen-netback/front testing
Date: Wed, 06 Aug 2014 13:53:10 -0700 (PDT) [thread overview]
Message-ID: <20140806.135310.1924341636144726761.davem@davemloft.net> (raw)
In-Reply-To: <1407349024-2489-1-git-send-email-zoltan.kiss@citrix.com>
From: Zoltan Kiss <zoltan.kiss@citrix.com>
Date: Wed, 6 Aug 2014 19:17:00 +0100
> This series is my work during stressing the xen network drivers, hopefully
> others can benefit from it.
> 1/4: Filling payload with pattern, useful for checking data correctness when the
> packets travelling without checksum (~ intrahost VM-to-VM). Already sent it
> separately few times, so its version number differs
> 2/4: fine-grained buffer geometrics
> 3/4: fix UDP checksuming
> 4/4: sending TCP GSO packets. This is an RFC yet, as I'm not certain about all
> things changed here
>
> Signed-off-by: Zoltan Kiss <zoltan.kiss@citrix.com>
Zoltan, please resubmit this after the merge window closes and I re-open
the net-next tree.
Thank you.
prev parent reply other threads:[~2014-08-06 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 18:17 [PATCH net-next 0/4 v5] pktgen: Upstreaming features useful for xen-netback/front testing Zoltan Kiss
2014-08-06 18:17 ` [PATCH net-next 1/4 v5] pktgen: Fill the payload optionally with a pattern Zoltan Kiss
2014-08-06 18:17 ` [PATCH net-next 2/4 v5] pktgen: Allow setting frag sizes individually Zoltan Kiss
2014-08-06 18:17 ` [PATCH net-next 3/4 v5] pktgen: Fixing UPD checksum calculation Zoltan Kiss
2014-08-06 18:17 ` [PATCH net-next 4/4 v5] pktgen: Allow sending IPv4 TCP packets Zoltan Kiss
2014-08-06 20:53 ` David Miller [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=20140806.135310.1924341636144726761.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=tgraf@suug.ch \
--cc=xen-devel@lists.xenproject.org \
--cc=zoltan.kiss@citrix.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).