@prakashsurya pushed 1 commit.
b7b7172 Update to AMI 2018.02.16 with OI Hipster + OpenZFS
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/openzfs/openzfs/pull/553/files/41f3ef81778c54233c522063baf2ae2ebcabccf0..b7b7172fe3015584173520f1
You can view, comment on, or merge this pull request online at:
https://github.com/openzfs/openzfs/pull/553
-- Commit Summary --
* Update AMI to OpenIndiana Hipster 2017.10
-- File Changes --
M Jenkinsfile (4)
M jenkins/jobs/build_install_media.groovy (1)
M jenkins/pipelines/b
This is supersceded by #552
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/423#issuecomment-366385789
--
openzfs-developer
Archives:
https://op
Going further than Robert here, after looking at how this ended up, and some
later work on other (unpublished) consumers of libfakekernel, I would not
advocate _not_ trying to have libfakekernel share a libutaskq library. The
libfakekernel one really needs to present a "kernel-like" thread mode
Reviewed by: Pavel Zakharov
Reviewed by: Matthew Ahrens
Reopening [PR 423](https://github.com/openzfs/openzfs/pull/423) rebased onto
trunk, will RTI promptly.
You can view, comment on, or merge this pull request online at:
https://github.com/openzfs/openzfs/pull/552
-- Commit Summary --
I will investigate the work needed to break the taskq implementation out of
libfakekernel, and into a new libutaskq library. I'll report back when I have
something reasonable to show. Thanks for all the input! I appreciate it.
--
You are receiving this because you are subscribed to this thread.
On 2/16/18 9:17 , Prakash Surya wrote:
> @rmustacc OK. So, if I'm understanding you correctly, you'd like us to take
> the taskq implementation from libfakekernel, move it into a new userspace
> library (e.g. libutaskq), and then make libfakekernel and libzfs consume this
> new library?
>
I gu
@prakashsurya You may count me as a reviewer if you wish to proceed down the
current path, though I am having some seconds thoughts based on Robert's
comments. We could break this up in a subsequent change I guess. I'd be okay
with that.
--
You are receiving this because you are subscribed t
On 2/16/18 9:17 , Prakash Surya wrote:
> @rmustacc OK. So, if I'm understanding you correctly, you'd like us to take
> the taskq implementation from libfakekernel, move it into a new userspace
> library (e.g. libutaskq), and then make libfakekernel and libzfs consume this
> new library?
>
I th
@rmustacc OK. So, if I'm understanding you correctly, you'd like us to take the
taskq implementation from libfakekernel, move it into a new userspace library
(e.g. libutaskq), and then make libfakekernel and libzfs consume this new
library?
--
You are receiving this because you are subscribed
@prakashsurya I do think libzfs in general being a consumer of a fake kernel
library is the wrong thing. I mean, wouldn't you say the same thing if it was
linked against libzpool? It feels like we're going to all these contortions to
emulate a kernel environment which we don't do for other code
rmustacc commented on this pull request.
> @@ -88,6 +89,9 @@
#include
#defineMAXISALEN 257 /* based on sysinfo(2) man page */
+static int mount_tq_nthr = 512;/* taskq threads for multi-threaded
mounting */
Well, it's pretty easy to go tune down the max lwps you h
rmustacc commented on this pull request.
> + */
+static void
+zfs_dispatch_mount(libzfs_handle_t *hdl, zfs_handle_t **handles,
+size_t num_handles, int idx, zfs_iter_f func, void *data, taskq_t *tq)
+{
+ mnt_param_t *mnt_param = zfs_alloc(hdl, sizeof (mnt_param_t));
+
+ mnt_param
@andy-js do you have any more questions/comments on this? can I count you as a
reviewer?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/536#issuecomment-366291880
Closed #549 via f21ea2c501969bdb031021b67b78d910f71ed3e9.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/549#event-1478151573
--
openzfs-develop
Closed #550.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/550#event-1478147171
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
Closed #545.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/545#event-1478147758
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
Closed #551.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/551#event-1478146816
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
Closed #546.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/546#event-1478099925
--
openzfs-developer
Archives:
https://openzfs.topicbox.com/gr
19 matches
Mail list logo
