Content-Type: multipart/mixed; boundary="===============1025473475838645637==" MIME-Version: 1.0 From: nufosmatic at nufosmatic.com Subject: [SPDK] Sanity check on execution model Date: Mon, 15 Mar 2021 21:45:08 +0000 Message-ID: <20210315214508.2868.49865@ml01.vlan13.01.org> List-ID: To: spdk@lists.01.org --===============1025473475838645637== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable I am having a terrible time getting my head wrapped around the execution mo= del. Probably the biggest problem is I started life showing flight simulato= r customers how to use interrupts instead of polling (because I worked for = a company that did interrupts very, VERY well). This polling executive is c= ompletely old-fashioned how they did it before interrupts and multi-process= ors kinda stuff. But, the basic benchmarks don't lie - I'm seeing about a 2= 0% plus-up in performance using SPDK over kernel drivers, so I've got to ju= st deal with it and get with the program. So I finally re-arranged hello_world_bdev using a state machine maintained = in a Poller, where hello_write and hello_read are called when the right sta= te is met and the callbacks handle the asynchrony and update the state. Thi= s seems like a good model moving forward, where as I scale from the single-= channel prototype to a multi-channel reality, and the number of cores I hav= e available does not exceed the number of channels in my application. Is this a sensible use of a Poller? --===============1025473475838645637==--