Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Gregory Etelson <gregory at weka.io>
To: spdk@lists.01.org
Subject: Re: [SPDK] [PATCH v2] igb_uio: issue FLR during open and release of device file
Date: Sun, 16 Jul 2017 07:22:04 +0300	[thread overview]
Message-ID: <4563824.ntyntO6lBN@polaris> (raw)
In-Reply-To: ED26CBA2FAD1BF48A8719AEF02201E3651230B20@SHSMSX103.ccr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Hello Shijith,

Please add the patch to uio_pci_generic.c file in Linux kernel
We experience similar faults with NVMe devices  

On Wednesday, 12 July 2017 06:40:55 IDT Tan, Jianfeng wrote:
> 
> > -----Original Message-----
> > From: Shijith Thotton [mailto:shijith.thotton(a)caviumnetworks.com]
> > Sent: Friday, July 7, 2017 7:14 PM
> > To: dev(a)dpdk.org
> > Cc: Yigit, Ferruh; Gregory Etelson; Thomas Monjalon; Stephen Hemminger;
> > Tan, Jianfeng; Lu, Wenzhuo
> > Subject: [PATCH v2] igb_uio: issue FLR during open and release of device file
> > 
> > Set UIO info device file operations open and release. Call pci reset
> > function inside open and release to clear device state at start and end.
> > Copied this behaviour from vfio_pci kernel module code. With this patch,
> > it is not mandatory to issue FLR by PMD's during init and close.
> > 
> > Bus master enable and disable are added in open and release respectively
> > to take care of device DMA.
> > 
> > Signed-off-by: Shijith Thotton <shijith.thotton(a)caviumnetworks.com>
> 
> Reviewed-by: Jianfeng Tan <jianfeng.tan(a)intel.com>


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5386 bytes --]

                 reply	other threads:[~2017-07-16  4:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4563824.ntyntO6lBN@polaris \
    --to=spdk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox