linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <keith.busch@intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	Wei Zhang <wzhang@fb.com>, Jens Axboe <axboe@fb.com>
Subject: Re: [PATCH 0/3] Limiting pci access requests
Date: Tue, 9 Aug 2016 12:36:33 -0500	[thread overview]
Message-ID: <20160809173633.GF27301@localhost> (raw)
In-Reply-To: <1470683667-28418-1-git-send-email-keith.busch@intel.com>

Hi Keith,

On Mon, Aug 08, 2016 at 01:14:24PM -0600, Keith Busch wrote:
> We observe that error handling and device hot removal creates many
> unnecessary config and memory accesses to devices, some of which are not
> even present. While we expect command processing to proceed, we observe
> on various platforms that the unnecessary accesses create instability
> with hardware performing completion synthesis, and slows down handling
> of such error events as well as normal IO processing.

Is there some hot removal path that we've suddenly starting exercising
more than we used to?  Can you give us any details of that?  I'm
wondering if there are any more generic fixes we can make.  These
patches seem good, but a little piece-meal, so it feels like there
could be more places where we trip over similar issues.

> This patch series aims to reduce unnecessary accesses.
> 
> Keith Busch (3):
>   pcie: Don't search capabilities on removed devices
>   pci/msix: Skip disabling removed devices
>   pcie/aer: Cache capability position
> 
>  drivers/pci/msi.c             |  5 +++++
>  drivers/pci/pci.c             |  2 +-
>  drivers/pci/pcie/aer/aerdrv.c | 38 +++++++++++++++++---------------------
>  drivers/pci/pcie/aer/aerdrv.h |  1 +
>  4 files changed, 24 insertions(+), 22 deletions(-)
> 
> -- 
> 2.7.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-08-09 17:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 19:14 [PATCH 0/3] Limiting pci access requests Keith Busch
2016-08-08 19:14 ` [PATCH 1/3] pcie: Don't search capabilities on removed devices Keith Busch
2016-08-18 22:38   ` Bjorn Helgaas
2016-08-08 19:14 ` [PATCH 2/3] pci/msix: Skip disabling " Keith Busch
2016-08-18 23:29   ` Bjorn Helgaas
2016-08-19 17:11     ` Keith Busch
2016-08-08 19:14 ` [PATCH 3/3] pcie/aer: Cache capability position Keith Busch
2016-08-09 17:33   ` Bjorn Helgaas
2016-09-06 21:05     ` Jon Derrick
2016-09-06 21:18       ` Keith Busch
2016-08-09 17:36 ` Bjorn Helgaas [this message]
2016-08-09 18:56   ` [PATCH 0/3] Limiting pci access requests Keith Busch
2016-08-09 18:56     ` Lukas Wunner
2016-08-17 21:05       ` Keith Busch
2016-08-18 14:02         ` Lukas Wunner
2016-08-18 16:05           ` Keith Busch
2016-08-18 16:59             ` Lukas Wunner

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=20160809173633.GF27301@localhost \
    --to=helgaas@kernel.org \
    --cc=axboe@fb.com \
    --cc=bhelgaas@google.com \
    --cc=keith.busch@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=wzhang@fb.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 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).