All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stojaczyk, Dariusz <dariusz.stojaczyk at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: Running SPDK without app framework
Date: Fri, 27 Mar 2020 12:52:25 +0000	[thread overview]
Message-ID: <a05ff480241b437da257097240e7858e@intel.com> (raw)
In-Reply-To: 26203033ee3e4e4bb44b58ed73e31917@intel.com

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

Bump. This is actually kicking me in the ass now. :) I would like to utilize spdk_app_opts->json_config_ignore_errors in fio_plugin, but there are no spdk_app_opts there.

We must get this straight. Let's put in the planning.

D.

      _____________________________________________
      From: Stojaczyk, Dariusz
      Sent: Monday, February 3, 2020 1:17 PM
      To: Zawadzki, Tomasz <tomasz.zawadzki(a)intel.com>
      Cc: Storage Performance Development Kit <spdk(a)lists.01.org>
      Subject: Running SPDK without app framework


      Tomek, I'm looking through your patch example/fio: add option to load json_config [1] and have some concerns to the overall design of applications utilizing SPDK without the app framework. First of all, we seem to use spdk_app_json_config_load() to load a JSON config in fio_plugin. The spdk_app_ prefix in that function suggests it's the app framework API, which we don't use in fio_plugin. I'm guessing it should be at least renamed? spdk_json_config_load() maybe?

      spdk_app_json_config_load() is defined in spdk_internal/event.h. Why is this internal anyway? This practically forces external SPDK users to stick with either legacy json config files, or spdk_app_start(). The question is where should we move it? lib/event.h is currently specific to the app framework. Do you have any plans for SPDK app design without the app framework? I'm guessing we do want to support it (see fio_plugin), but currently it's messy.

      D.

      [1] https://review.gerrithub.io/c/spdk/spdk/+/463979/



                 reply	other threads:[~2020-03-27 12:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a05ff480241b437da257097240e7858e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.