[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libguestfs
Subject:    [Libguestfs] [libnbd] How close are we to declaring a stable API?
From:       "Richard W.M. Jones" <rjones () redhat ! com>
Date:       2019-06-29 10:25:02
Message-ID: 20190629102502.GG3888 () redhat ! com
[Download RAW message or body]

As the subject says, how close are we to being able to declare a
stable API for libnbd?

I believe these are the main topics:

* Do we need to have an extra thread for writing?  I'm unclear about
  whether b92392b717 (which allows the state machine to break during
  reply processing) means we definitely don't need threads.  I imagine
  that two threads doing simultaneous send(2) and recv(2) calls could
  still improve performance (eg. having two cores copying skbs from
  userspace to and from kernel).

* Should ‘nbd_shutdown' take an extra parameter to indicate that it
  should be delayed until all commands in the queue are retired?

Is there anything else?

We could also consider doing a "soft stable API" release where we bump
the version up to 0.9.x, announce that we're going to make the API
stable soon, have a much higher bar for breaking the API, but don't
actually prevent API breaks in cases where it's necessary.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

_______________________________________________
Libguestfs mailing list
Libguestfs@redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
[prev in list] [next in list] [prev in thread] [next in thread]