From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============6373501940914547407=="
MIME-Version: 1.0
From: Harris, James R <james.r.harris at intel.com>
Subject: Re: [SPDK] MIgrating code from v18.xx to v19.07
Date: Thu, 19 Sep 2019 16:00:50 +0000
Message-ID: <CBDA5208-A7AE-4FAA-BB5D-DC0ECA5EE95A@intel.com>
List-ID: <spdk@lists.01.org>
To: spdk@lists.01.org

--===============6373501940914547407==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Hi Jan,

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

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

-Jim



=EF=BB=BFOn 9/19/19, 8:38 AM, "SPDK on behalf of Lisowiec, Jan" <spdk-bounc=
es(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 v=
19.07.
    =

    The code implements a simple poller by means of spdk_ring_create(), spd=
k_allocate_thread() and a callback that enqueues messages on the ring. In v=
19.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 wh=
at 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-5=
2-316 | Kapital zakladowy 200.000 PLN.
    =

    Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adre=
sata i moze zawierac informacje poufne. W razie przypadkowego otrzymania te=
j wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; ja=
kiekolwiek
    przegladanie lub rozpowszechnianie jest zabronione.
    This e-mail and any attachments may contain confidential material for t=
he sole use of the intended recipient(s). If you are not the intended recip=
ient, please contact the sender and delete all copies; any review or distri=
bution by
    others is strictly prohibited.
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://lists.01.org/mailman/listinfo/spdk
    =



--===============6373501940914547407==--