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] pktgen: Allow setting frag sizes individually
Date: Tue, 01 Jul 2014 12:14:53 -0700 (PDT) [thread overview]
Message-ID: <20140701.121453.646524500364143878.davem@davemloft.net> (raw)
In-Reply-To: <1403728972-29548-3-git-send-email-zoltan.kiss@citrix.com>
From: Zoltan Kiss <zoltan.kiss@citrix.com>
Date: Wed, 25 Jun 2014 21:42:51 +0100
> By defining the number of frags via "nfrags", their sizes get calculated by
> pktgen. This patch allows their offsets and sizes to be specified via
> "frag_off-len", in a comma separated list (e.g.
> "frag_off-len 0-1,500-200,5000-10,9-100). The first is the offset
> (0 <= offset < 2^16), second is size (0 < length <= 65536). This also determines
> the number of frags, so it overwrites "frags" (and vice versa, "frags"
> invalidate this setting)
> xen-netback is prone to have problem with compound pages, as the memory granting
> interface can only handle 4k pages. This extension of pktgen is proven to be
> useful to test that.
>
> Signed-off-by: Zoltan Kiss <zoltan.kiss@citrix.com>
Can you respin these against current net-next and repost, thanks Zoltan.
next prev parent reply other threads:[~2014-07-01 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 20:42 [PATCH net-next] pktgen: Upstreaming features useful for xen-netback/front testing Zoltan Kiss
2014-06-25 20:42 ` [PATCH net-next v3] pktgen: Fill the payload optionally with a pattern Zoltan Kiss
2014-06-25 20:42 ` [PATCH net-next] pktgen: Allow setting frag sizes individually Zoltan Kiss
2014-07-01 19:14 ` David Miller [this message]
2014-06-25 20:42 ` [PATCH net-next 3/3 RFC] pktgen: Allow sending TCP packets Zoltan Kiss
2014-06-26 0:41 ` Cong Wang
2014-06-26 0:44 ` David Miller
2014-06-26 9:39 ` Zoltan Kiss
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=20140701.121453.646524500364143878.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).