From: Greg KH <greg@kroah.com>
To: Aritz Bastida <aritzbastida@gmail.com>
Cc: Antonio Vargas <windenntw@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Right way to configure a driver? (sysfs, ioctl, proc, configfs,....)
Date: Mon, 30 Jan 2006 13:39:08 -0800 [thread overview]
Message-ID: <20060130213908.GA26463@kroah.com> (raw)
In-Reply-To: <7d40d7190601300323t1aca119ci@mail.gmail.com>
On Mon, Jan 30, 2006 at 12:23:14PM +0100, Aritz Bastida wrote:
> Thank you Antonio and Greg
> But I still have one question pending:
>
> > >
> > > 3.- Actually the most difficult config I must do is to pass three
> > > values from userspace to my module. Specifically two integers and a
> > > long (it's an offset to a memory zone I've previously defined)
> > >
> > > struct meminfo {
> > > unsigned int id; /* segment identifier */
> > > unsigned int size; /* size of the memory area */
> > > unsigned long offset; /* offset to the information */
> > > };
> > >
> > > How would you pass this information in sysfs? Three values in the same
> > > file? Note that using three different files wouldn't be atomic, and I
> > > need atomicity.
> > >
>
> I guess I could pass three values on the same file, like this:
> $ echo "5 1000 500" > meminfo
>
> I know that breaks the sysfs golden-rule, but how can I pass those
> values _atomically_ then? Having three different files wouldn't be
> atomic...
That's what configfs was created for. I suggest using that for things
like this, as sysfs is not intended for it.
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-30 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 20:06 Right way to configure a driver? (sysfs, ioctl, proc, configfs,....) Aritz Bastida
2006-01-27 5:01 ` Greg KH
2006-01-27 10:30 ` Aritz Bastida
[not found] ` <69304d110601270834q5fa8a078m63a7168aa7e288d1@mail.gmail.com>
2006-01-30 11:23 ` Aritz Bastida
2006-01-30 21:39 ` Greg KH [this message]
2006-02-01 14:54 ` Jan Engelhardt
2006-02-01 15:11 ` Greg KH
2006-02-01 15:44 ` Aritz Bastida
2006-02-01 16:17 ` Jan Engelhardt
2006-02-02 6:31 ` Neil Brown
2006-01-30 21:41 ` Greg KH
2006-02-01 13:37 ` Aritz Bastida
2006-02-01 13:53 ` linux-os (Dick Johnson)
2006-02-01 14:19 ` Aritz Bastida
2006-02-01 15:11 ` linux-os (Dick Johnson)
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=20060130213908.GA26463@kroah.com \
--to=greg@kroah.com \
--cc=aritzbastida@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=windenntw@gmail.com \
/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.