Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Sreeni (Sreenivasa) Busam (Stellus) <s.busam at stellus.com>
To: spdk@lists.01.org
Subject: [SPDK] Question regarding async event in target.
Date: Tue, 17 Apr 2018 23:38:49 +0000	[thread overview]
Message-ID: <4999d0419911439b9174d364ad1caffe@stellus.com> (raw)
In-Reply-To: CGME20180417233850uscas1p10f3d45b6ac7ac112a68907bcccfc2195@uscas1p1.samsung.com

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

Hello,

I am looking at how to register async events from initiator to target and handle SSD controller errors in the NVMF target. From the code in NVMF, I see there is only 1 async request. Is it not possible to have multiple async requests registered from initiator and handled between initiator and target?
Please let me know how to setup multiple requests at the same time. If you know how different controller errors can be handled, let me know.
spdk_nvmf_session_async_event_request(struct spdk_nvmf_request *req)
{
    struct spdk_nvmf_session *session = req->conn->sess;
    struct spdk_nvme_cpl *rsp = &req->rsp->nvme_cpl;

    assert(session->vcdata.aerl + 1 == 1);
    if (session->aer_req != NULL) {
        SPDK_TRACELOG(SPDK_TRACE_NVMF, "AERL exceeded\n");
        rsp->status.sct = SPDK_NVME_SCT_COMMAND_SPECIFIC;
        rsp->status.sc = SPDK_NVME_SC_ASYNC_EVENT_REQUEST_LIMIT_EXCEEDED;
        return SPDK_NVMF_REQUEST_EXEC_STATUS_COMPLETE;
    }
    session->aer_req = req;

I appreciate your help.
Thank you,
Sreeni

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

             reply	other threads:[~2018-04-17 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 23:38 Sreeni Busam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-18  0:21 [SPDK] Question regarding async event in target Verkamp, Daniel

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=4999d0419911439b9174d364ad1caffe@stellus.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