My guess is that you probably don't want exactly the same semantics and calling conventions in a kernel. But if you're on the same platform, why not just use the IPCs that you already have there (shared memory/copyin/copyout, even doors on some platforms). In a kernel, you *know* the other end is there, and there is no room for breakage in the middle. On Wed, Sep 3, 2014 at 9:31 PM, Martin Sustrik <sustrik@xxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I've been aiming for that kind of thing for a long time, here is, for > example, a proof of concept for Linux kernel: > > https://github.com/250bpm/linux-2.6/tree/sp-v2.6.36 > > - From the technical point of view, nanomsg has no dependencies, except > for C runtime. Thus, when moving the code to the kernel you would have > to emulate using user-space calls (e.g. socket API) from inside of the > kernel. Not sure how easy is that in BSD kernel. In Linux kernel, at > least, it's not entirely trivial. > > Martin > > On 04/09/14 00:27, Sideropoulos, Alexander wrote: > > Hey all. I have posted this question to StackOverflow, but there is > > little nanomsg traction on that site (for now). > > > > > http://stackoverflow.com/questions/25576195/using-nanomsg-in-kernel-space > > > > I am essentially looking to get nanomsg working in kernel-space > > (FreeBSD) with an end-goal of sending/receiving messages between > > kernel and user threads. Any thoughts? > > > > Thanks! ---------- Alexander P. Sideropoulos NetApp -- Performance > > Engineering siderop1@xxxxxxxxxx > > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJUB+sxAAoJENTpVjxCNN9YGLMH+gPnioxEYwOxJW1LQSFNx1D/ > 6xHP2V0XelS7868yS1FhYhFbnAbq32aVcwxilETdB56RDy3xwYVY4vGIUpClijHf > 5hslPGryykvP7QvjDVfGDkXuxTdjV0tUo5s9MvGQQIAu2Zcg7HkMkTHlEeuedn+K > GjUFDdWBReJOHP+1tRa/ow+lGIdl/SnenpxV7P5gmQwWxHY+nzXvDwflh4JuC3aJ > /WnO8truuSIHnPflkvXQT7K2OFY9Yj8jW4EzD3NNZprDYzUqde/4xncXRnwPzIlQ > hoRVso4eGJZFVijW4xRqgMvNIs0kw+MZbTpaGPblf00mUhXEisp68bJAUbxjOXA= > =SB7V > -----END PGP SIGNATURE----- > >