Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Freeman Zhang <freeman.zhang1992 at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] "Requested device XXX cannot be used" warning in device detach procedure may be misleading
Date: Mon, 13 Mar 2017 12:28:58 +0800	[thread overview]
Message-ID: <8b74f6ae-5d34-3934-06d2-f30ed72159e4@gmail.com> (raw)
In-Reply-To: 2BFA8F2383C3784C90698C10BC0963195EEC2867@SHSMSX103.ccr.corp.intel.com

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

Hi

On 3/13/17 12:03 PM, Chang, Cunyin wrote:
> 
> Actually, the error message caused by the function spdk_pci_device_detach(), after we detach the device, we try to call the function
> rte_eal_pci_probe_one(), but we do not have callback function for the dpdk nvme driver at this point, so the error message show up, 
> but  this function will add the device back to dpdk pci device list, then we could probe the device next time when
> we want to use it again. So it has no adverse effects but just one error message, but we still trying to fix it now.
> 

Thanks for your reply!

I've noticed it and that is why I think it's kind of misleading. So I
guess we should not focus only on reusing codes but also making it
clearer for both users and developers.


All the best!
Freeman


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

             reply	other threads:[~2017-03-13  4:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13  4:28 Freeman Zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-13 16:10 [SPDK] "Requested device XXX cannot be used" warning in device detach procedure may be misleading Walker, Benjamin
2017-03-13  4:03 Chang, Cunyin
2017-03-12  3:43 Freeman Zhang

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=8b74f6ae-5d34-3934-06d2-f30ed72159e4@gmail.com \
    --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