From: David Miller <davem@davemloft.net>
To: David.Laight@ACULAB.COM
Cc: netdev@vger.kernel.org, bruce.w.allan@intel.com,
jeffrey.e.pieper@intel.com, jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH net 1/1] e1000e: Stop tx/rx setup spinning for upwards of 300us.
Date: Tue, 03 Mar 2020 16:02:06 -0800 (PST) [thread overview]
Message-ID: <20200303.160206.1467881674346759532.davem@davemloft.net> (raw)
In-Reply-To: <6ef1e257642743a786c8ddd39645bba3@AcuMS.aculab.com>
From: David Laight <David.Laight@ACULAB.COM>
Date: Tue, 3 Mar 2020 17:06:03 +0000
> Reduce the delay between checks for the ME being idle from 50us
> to uus.
^^^
I think you mean '5us' here.
I'll let the Intel folks review and integrate this as it's a
non-trivial change honestly.
next prev parent reply other threads:[~2020-03-04 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 17:06 [PATCH net 1/1] e1000e: Stop tx/rx setup spinning for upwards of 300us David Laight
2020-03-04 0:02 ` David Miller [this message]
2020-03-04 9:44 ` David Laight
2020-03-04 18:03 ` Jeff Kirsher
2020-03-26 11:08 ` David Laight
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=20200303.160206.1467881674346759532.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@ACULAB.COM \
--cc=bruce.w.allan@intel.com \
--cc=jeffrey.e.pieper@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.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 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).