From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/4] network: add test for low latency busy poll
Date: Tue, 27 Oct 2015 18:26:29 +0100 [thread overview]
Message-ID: <20151027172629.GA31866@rei> (raw)
In-Reply-To: <562F7276.5090807@oracle.com>
Hi!
> Any comments regarding this patch-set?
I looked at the code and it looks good. I haven't looked deeper into the
features it tries to test though.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2015-10-27 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:47 [LTP] [PATCH 1/4] network: add test for low latency busy poll Alexey Kodanev
2015-09-16 9:47 ` [LTP] [PATCH 2/4] network/tcp_fastopen: add SO_BUSY_POLL sockoption Alexey Kodanev
2015-09-16 9:47 ` [LTP] [PATCH 3/4] lib/test_net.sh: allow any additional options to tst_netload Alexey Kodanev
2015-09-16 9:47 ` [LTP] [PATCH 4/4] network: add test for busy poll with setting it per socket Alexey Kodanev
2015-10-27 12:47 ` [LTP] [PATCH 1/4] network: add test for low latency busy poll Alexey Kodanev
2015-10-27 17:26 ` Cyril Hrubis [this message]
2015-10-28 7:11 ` Alexey Kodanev
2015-10-29 11:06 ` Alexey Kodanev
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=20151027172629.GA31866@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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