[00:22:05] *** Joins: tomzawadzki (~tzawadzk@134.134.137.71) [07:10:00] *** Quits: tomzawadzki (~tzawadzk@134.134.137.71) (Ping timeout: 240 seconds) [12:40:54] https://github.com/axboe/fio/issues/408 [12:41:06] https://github.com/axboe/fio/pull/409 [12:41:17] I just filed and partially fixed that fio problem [12:41:36] it's an annoyance with the spdk fio plugins because we have plugin-specific options [13:13:24] *** Quits: dwaddington (Daniel@nat/ibm/x-dpoivupoagzjzoio) (Ping timeout: 268 seconds) [13:48:42] so are there are any presos, wikis, faqs anywhere on "SPDK app framework 101"? [13:50:43] Daniel's talk from the summit [13:53:00] OK, yeah got that one of course [13:55:33] bwalker, a few assumptions if you can confirm for me on what you had in mind with the blob hello world... use app framework, run on top of a bdev, leverage the blob_bdev helper functions. Those sound about right? Missing any other key things? [13:57:47] that sounds exactly right [13:58:35] cool, and cmd line exposing all major top level API - nothing fancy yeah? [13:58:36] you can copy a lot from test/lib/blobfs/mkfs/mkfs [13:58:44] basically, just start with that tool [13:58:47] yeah, I've been looking at that one for sure [13:58:52] and then keep going after it formats the disk [13:58:57] to create blobs and such [13:59:03] no command line options at all preferably [13:59:29] it's just an example - just choose to do something arbitrary like make a blobstore, create some blobs, read/write, shutdown, etc. [13:59:55] hmmmm, really? I was thinking create/delete/list/read/write maybe dump md or something like that? What were you envisioning that it actually do? [14:00:18] it's a tutorial [14:00:24] like examples/nvme/hello_world [14:00:33] it does nothing useful in and of itself [14:00:46] what's useful is that it does some arbitrary things and explains how it does them with lots of comments [14:01:10] ahh, OK. cmd line driven might be useful as more than just a sequential example though don't you think? [14:01:24] yeah, agree with what you say of course [14:01:39] I don't want to feature creep it because then it loses its impact as the simplest example of what to do [14:01:53] we can have more than one example, just like we do for nvme [14:01:59] for sure [14:02:10] where hello_world does barely anything, but then we have more advanced examples that may accomplish useful work [14:02:36] hey peluse, sorry we haven't gotten to your NVMe UT reviews yet - once the release stuff has quieted down, we should be able to get back to them [14:03:38] no prob, I doubt it will be hard to rebase as there shouldn't be too many conflicts I hope :) [14:06:29] bwalker, cool. I'll do it that way. thx [14:10:29] so is the shutdown callback that we can optionally provide in the opts struct just invoked on abnormal termination of some kind of the thread that we start in spdk_app_start() or does it have some other specific or general purpose? [14:11:12] it's invoked in response to a signal handler for ctrl-c [14:13:47] ahh, OK I see it now. SIGINT registration in spdk_app_start(). OK, I'll start RTFC now :) [14:20:55] bwalker, we don't want any dependencies on blobfs in here though correct? [14:21:28] correct - just blobstore [14:21:39] gracias [18:19:47] haven't been around for a few days but FYI just had a doc change fail in CI on run_test ./test/vhost/spdk_vhost.sh --integrity so don't know if that's a known thing as of now or not.... [18:23:53] *** Joins: ziyeyang_ (~ziyeyang@192.55.54.40) [22:03:39] *** Joins: tomzawadzki (~tzawadzk@134.134.139.77) [23:15:47] *** Quits: gila (~gila@5ED4FE92.cm-7-5d.dynamic.ziggo.nl) (Quit: My Mac Pro has gone to sleep. ZZZzzz…)