From: David Miller <davem@davemloft.net>
To: brouer@redhat.com
Cc: netdev@vger.kernel.org, robert@herjulf.se, robert.hu@intel.com,
pabeni@redhat.com, kafai@fb.com, tariqt@mellanox.com
Subject: Re: [net-next PATCH 0/4] Updates for samples/pktgen
Date: Thu, 02 Nov 2017 14:20:20 +0900 (KST) [thread overview]
Message-ID: <20171102.142020.275473805803540023.davem@davemloft.net> (raw)
In-Reply-To: <150953283424.29671.6809291616813585256.stgit@firesoul>
From: Jesper Dangaard Brouer <brouer@redhat.com>
Date: Wed, 01 Nov 2017 11:41:04 +0100
> This patchset updates samples/pktgen and synchronize with changes
> maintained in https://github.com/netoptimizer/network-testing/
>
> Features wise Robert Hoo <robert.hu@intel.com> added support for
> detecting and determining dev NUMA node IRQs, and added a new script
> named pktgen_sample06_numa_awared_queue_irq_affinity.sh that use these
> features.
>
> Cleanup remove last of the old sample files, as IPv6 is covered by
> existing sample code.
Series applied, thanks Jesper.
prev parent reply other threads:[~2017-11-02 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 10:41 [net-next PATCH 0/4] Updates for samples/pktgen Jesper Dangaard Brouer
2017-11-01 10:41 ` [net-next PATCH 1/4] samples/pktgen: Add some helper functions Jesper Dangaard Brouer
2017-11-01 10:41 ` [net-next PATCH 2/4] samples/pktgen: add script pktgen_sample06_numa_awared_queue_irq_affinity.sh Jesper Dangaard Brouer
2017-11-01 10:41 ` [net-next PATCH 3/4] samples/pktgen: update sample03, no need for clones when bursting Jesper Dangaard Brouer
2017-11-01 10:41 ` [net-next PATCH 4/4] samples/pktgen: remove remaining old pktgen sample scripts Jesper Dangaard Brouer
2017-11-01 16:28 ` [net-next PATCH 0/4] Updates for samples/pktgen Alexei Starovoitov
2017-11-02 5:20 ` 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=20171102.142020.275473805803540023.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robert.hu@intel.com \
--cc=robert@herjulf.se \
--cc=tariqt@mellanox.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).