Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] MIgrating code from v18.xx to v19.07
Date: Thu, 19 Sep 2019 16:00:50 +0000	[thread overview]
Message-ID: <CBDA5208-A7AE-4FAA-BB5D-DC0ECA5EE95A@intel.com> (raw)

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

Hi Jan,

We've moved the poller (and associated message) management into the spdk_thread itself.  You should now be able to just do something like this:

thread = spdk_thread_create("jans_thread", NULL);
spdk_set_thread(thread);
poller = spdk_poller_register(...);
spdk_thread_poll(thread, 0, 0);

-Jim



On 9/19/19, 8:38 AM, "SPDK on behalf of Lisowiec, Jan" <spdk-bounces(a)lists.01.org on behalf of jan.lisowiec(a)intel.com> wrote:

    Hi Everyone,
    
    I'm in a process of migrating some piece of logic from spdk v18.xx to v19.07.
    
    The code implements a simple poller by means of spdk_ring_create(), spdk_allocate_thread() and a callback that enqueues messages on the ring. In v19.07 spdk_allocate_thread() is no longer available. Is there a new way of achieving the same ? I've found examples/bdev/fio_plugin, which might be what I'm looking for but I wonder if I need all of it to implement my simple poller.
    
    Can somebody provide some guidelines ?
    
    Thanks
    Jan
    --------------------------------------------------------------------
    
    Intel Technology Poland sp. z o.o.
    ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
    
    Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
    przegladanie lub rozpowszechnianie jest zabronione.
    This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by
    others is strictly prohibited.
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://lists.01.org/mailman/listinfo/spdk
    


             reply	other threads:[~2019-09-19 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 16:00 Harris, James R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-19 16:10 [SPDK] MIgrating code from v18.xx to v19.07 Walker, Benjamin
2019-09-19 15:37 Lisowiec, Jan

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=CBDA5208-A7AE-4FAA-BB5D-DC0ECA5EE95A@intel.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