All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: Alex_Gagniuc@Dellteam.com, lukas@wunner.de
Cc: mr.nuke.me@gmail.com, keith.busch@intel.com,
	linux-pci@vger.kernel.org, Austin.Bolen@dell.com,
	Stuart.Hayes@dell.com, Narendra.K@dell.com,
	Christopher.Arzola@dell.com, David.Chalfant@dell.com
Subject: Re: Should a PCIe Link Down event set the PCI_DEV_DISCONNECTED bit?
Date: Fri, 27 Jul 2018 11:17:49 -0700	[thread overview]
Message-ID: <a7c024d3-4111-bbd2-68e9-2122be083cf7@kernel.org> (raw)
In-Reply-To: <99604d46a7554eb38ee6c1579c53d835@ausx13mps321.AMER.DELL.COM>

On 7/27/2018 10:51 AM, Alex_Gagniuc@Dellteam.com wrote:
>> The first problem with that patch was that I hadn't fully understood
>> yet when to set PCI_DEV_DISCONNECTED and when not to set it.
> I think PCI_DEV_DISCONNECTED is a documentation issue above all else.
> The history I was given is that drivers would take a very long time to
> tear down a device. Config space IO to an nonexistent device took a long
> while to time out. Performance was one motivation -- and was not documented.
> 

Completion timeouts are typically in the orders of 50ms. If you have a
lot of outstanding non-posted requests, it will take time for SW to
flush all requests.

  reply	other threads:[~2018-07-27 19:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 22:38 Should a PCIe Link Down event set the PCI_DEV_DISCONNECTED bit? Alex G.
2018-07-26 23:00 ` Rajat Jain
2018-07-27  0:04   ` Alex_Gagniuc
2018-07-27  7:18 ` Lukas Wunner
2018-07-27 15:52   ` Alex_Gagniuc
2018-07-27 17:05     ` Lukas Wunner
2018-07-27 17:51       ` Alex_Gagniuc
2018-07-27 18:17         ` Sinan Kaya [this message]
2018-07-27 18:23           ` Alex_Gagniuc
2018-07-27 18:34             ` Sinan Kaya
2018-07-28 18:31         ` Lukas Wunner
2018-07-29  0:26           ` Sinan Kaya
2018-07-29 12:09             ` Lukas Wunner
2018-07-29 16:59               ` Sinan Kaya
2018-07-30 13:28           ` David Laight
2018-07-30 13:54             ` Lukas Wunner
2018-07-30 16:06               ` David Laight
2018-07-30 21:38           ` Alex_Gagniuc
2018-07-31  9:28             ` Lukas Wunner
2018-07-31 16:35               ` Alex_Gagniuc
2018-08-01  8:58                 ` David Laight
2018-08-01 19:06                   ` Alex_Gagniuc

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=a7c024d3-4111-bbd2-68e9-2122be083cf7@kernel.org \
    --to=okaya@kernel.org \
    --cc=Alex_Gagniuc@Dellteam.com \
    --cc=Austin.Bolen@dell.com \
    --cc=Christopher.Arzola@dell.com \
    --cc=David.Chalfant@dell.com \
    --cc=Narendra.K@dell.com \
    --cc=Stuart.Hayes@dell.com \
    --cc=keith.busch@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mr.nuke.me@gmail.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.