From: Rick Lindsley <ricklind@linux.vnet.ibm.com>
To: Lijun Pan <lijunp213@gmail.com>,
Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Cc: Lijun Pan <ljp@linux.vnet.ibm.com>,
Dany Madden <drt@linux.ibm.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Tom Falcon <tlfalcon@linux.ibm.com>,
netdev@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V2 net] ibmvnic: Continue with reset if set link down failed
Date: Thu, 22 Apr 2021 00:05:55 -0700 [thread overview]
Message-ID: <376383c3-3fbd-25bf-8fb3-6cd54c218e34@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOhMmr4ckVFTZtSeHFHNgGPUA12xYO8WcUoakx7WdwQfSKBJhA@mail.gmail.com>
On 4/21/21 10:06 PM, Lijun Pan wrote:
> No real customer runs the system under that heavy load created by
> HTX stress test, which can tear down any working system.
So, are you saying the bugs that HTX uncovers are not worth fixing?
There's a fair number of individuals and teams out there that
utilize HTX in the absence of such a workload, and not just for vnic.
What workload would you suggest to better serve "real customers"?
> I think such optimizations are catered for passing HTX tests.
Well, yes. If the bugs are found with HTX, the fixes are verified
against HTX. If they were found with a "real customer workload" they'd
be verified against a "real customer workload."
WARNING: multiple messages have this Message-ID (diff)
From: Rick Lindsley <ricklind@linux.vnet.ibm.com>
To: Lijun Pan <lijunp213@gmail.com>,
Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Cc: netdev@vger.kernel.org, Lijun Pan <ljp@linux.vnet.ibm.com>,
Tom Falcon <tlfalcon@linux.ibm.com>,
Paul Mackerras <paulus@samba.org>,
Dany Madden <drt@linux.ibm.com>, Jakub Kicinski <kuba@kernel.org>,
linuxppc-dev@lists.ozlabs.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH V2 net] ibmvnic: Continue with reset if set link down failed
Date: Thu, 22 Apr 2021 00:05:55 -0700 [thread overview]
Message-ID: <376383c3-3fbd-25bf-8fb3-6cd54c218e34@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOhMmr4ckVFTZtSeHFHNgGPUA12xYO8WcUoakx7WdwQfSKBJhA@mail.gmail.com>
On 4/21/21 10:06 PM, Lijun Pan wrote:
> No real customer runs the system under that heavy load created by
> HTX stress test, which can tear down any working system.
So, are you saying the bugs that HTX uncovers are not worth fixing?
There's a fair number of individuals and teams out there that
utilize HTX in the absence of such a workload, and not just for vnic.
What workload would you suggest to better serve "real customers"?
> I think such optimizations are catered for passing HTX tests.
Well, yes. If the bugs are found with HTX, the fixes are verified
against HTX. If they were found with a "real customer workload" they'd
be verified against a "real customer workload."
next prev parent reply other threads:[~2021-04-22 7:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 21:35 [PATCH V2 net] ibmvnic: Continue with reset if set link down failed Dany Madden
2021-04-20 21:35 ` Dany Madden
2021-04-20 21:42 ` Lijun Pan
2021-04-20 21:42 ` Lijun Pan
2021-04-21 6:45 ` Sukadev Bhattiprolu
2021-04-21 6:45 ` Sukadev Bhattiprolu
2021-04-22 5:06 ` Lijun Pan
2021-04-22 5:06 ` Lijun Pan
2021-04-22 6:58 ` Sukadev Bhattiprolu
2021-04-22 6:58 ` Sukadev Bhattiprolu
2021-04-22 7:05 ` Rick Lindsley [this message]
2021-04-22 7:05 ` Rick Lindsley
2021-04-22 17:21 ` Michal Suchánek
2021-04-22 17:21 ` Michal Suchánek
2021-04-22 17:38 ` Lijun Pan
2021-04-22 17:38 ` Lijun Pan
2021-04-23 2:26 ` Rick Lindsley
2021-04-23 2:26 ` Rick Lindsley
2021-05-04 19:05 ` Dany Madden
2021-05-04 19:05 ` Dany Madden
2021-04-21 7:54 ` Rick Lindsley
2021-04-21 7:54 ` Rick Lindsley
2021-04-22 5:12 ` Lijun Pan
2021-04-22 5:12 ` Lijun Pan
2021-04-22 7:05 ` Rick Lindsley
2021-04-22 7:05 ` Rick Lindsley
2021-04-22 5:30 ` Lijun Pan
2021-04-22 5:30 ` Lijun Pan
2021-04-22 7:07 ` Rick Lindsley
2021-04-22 7:07 ` Rick Lindsley
2021-04-22 17:01 ` Lijun Pan
2021-04-22 17:01 ` Lijun Pan
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=376383c3-3fbd-25bf-8fb3-6cd54c218e34@linux.vnet.ibm.com \
--to=ricklind@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=drt@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=lijunp213@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljp@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sukadev@linux.ibm.com \
--cc=tlfalcon@linux.ibm.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 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.