mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniele Orlandi <daniele@orlandi.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Passing references to kobjects between userland and kernel
Date: Tue, 20 Jun 2006 01:48:54 +0200	[thread overview]
Message-ID: <200606200148.56117.daniele@orlandi.com> (raw)
In-Reply-To: <20060616235800.GA29573@kroah.com>

On Saturday 17 June 2006 01:58, Greg KH wrote:
>
> Use the kobject_uevent() call from kernelspace to let userspace know
> whatever you want it to.  That is what it is there for :)

kobject_uevent() is fine if I want to asynchronously notify the user space of 
an event.

What I need is a synchronous bidirectional interface, e.g. I tell the kernel 
"connect node X with node Y" and I get back the resulting pipeline 
identifier.

> Or use configfs :)

Configfs is very interesting, it's surely well suited for several tasks I'm 
doing and I will add support for it into my subsystem.

What it's missing is the ability to create non-persistent configurations, 
bound to a process and disappearing along with the process that created them.

For example, my process creates pipelines between nodes using a ioctl() 
interface. If the process dies unexpectedly the file descriptor is 
automatically closed and I can release all the pipelines. I don't see a way I 
could accomplish the same with configfs or sysfs. 

OTOH, for what concerns persistent pipelines, configfs is quite good. It would 
be even better if I could create links from configfs objects to sysfs 
objects.

Bye,

-- 
  Daniele "Vihai" Orlandi

  reply	other threads:[~2006-06-19 23:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 14:26 Daniele orlandi
2006-06-16 23:58 ` Greg KH
2006-06-19 23:48   ` Daniele Orlandi [this message]
2006-06-19 23:53     ` Greg KH
2006-06-20  7:17       ` Daniele Orlandi

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=200606200148.56117.daniele@orlandi.com \
    --to=daniele@orlandi.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®