From: Willy Tarreau <w@1wt.eu>
To: lkp@lists.01.org
Subject: Re: [tcp] e926147618: stress-ng.icmp-flood.ops_per_sec -8.7% regression
Date: Wed, 08 Jun 2022 09:34:41 +0200 [thread overview]
Message-ID: <20220608073441.GE7547@1wt.eu> (raw)
In-Reply-To: <CACi_AuAr70bDB79zg9aAF1rD7e1qGgFwCGCAPYtS-zCp_zA0iw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
On Wed, Jun 08, 2022 at 10:26:12AM +0300, Moshe Kol wrote:
> Hmm, How is the ICMP flood stress test related to TCP connections?
To me it's not directly related, unless the test pre-establishes many
connections, or is affected in a way or another by a larger memory
allocation of this part.
Willy
WARNING: multiple messages have this Message-ID (diff)
From: Willy Tarreau <w@1wt.eu>
To: Moshe Kol <moshe.kol@mail.huji.ac.il>
Cc: kernel test robot <oliver.sang@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Yossi Gilad <yossi.gilad@mail.huji.ac.il>,
Amit Klein <aksecurity@gmail.com>,
Eric Dumazet <edumazet@google.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, lkp@lists.01.org, lkp@intel.com,
ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@linux.intel.com, fengwei.yin@intel.com
Subject: Re: [tcp] e926147618: stress-ng.icmp-flood.ops_per_sec -8.7% regression
Date: Wed, 8 Jun 2022 09:34:41 +0200 [thread overview]
Message-ID: <20220608073441.GE7547@1wt.eu> (raw)
In-Reply-To: <CACi_AuAr70bDB79zg9aAF1rD7e1qGgFwCGCAPYtS-zCp_zA0iw@mail.gmail.com>
On Wed, Jun 08, 2022 at 10:26:12AM +0300, Moshe Kol wrote:
> Hmm, How is the ICMP flood stress test related to TCP connections?
To me it's not directly related, unless the test pre-establishes many
connections, or is affected in a way or another by a larger memory
allocation of this part.
Willy
next prev parent reply other threads:[~2022-06-08 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 6:08 [tcp] e926147618: stress-ng.icmp-flood.ops_per_sec -8.7% regression kernel test robot
2022-06-08 6:08 ` kernel test robot
2022-06-08 6:48 ` Willy Tarreau
2022-06-08 6:48 ` Willy Tarreau
2022-06-08 7:26 ` Moshe Kol
2022-06-08 7:34 ` Willy Tarreau [this message]
2022-06-08 7:34 ` Willy Tarreau
2022-06-08 8:55 ` Yin Fengwei
2022-06-13 2:09 ` Feng Tang
2022-06-13 2:09 ` Feng Tang
2022-06-13 17:10 ` Eric Dumazet
2022-06-13 17:10 ` Eric Dumazet
2022-06-14 0:42 ` Feng Tang
2022-06-14 0:42 ` Feng Tang
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=20220608073441.GE7547@1wt.eu \
--to=w@1wt.eu \
--cc=lkp@lists.01.org \
/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.