From: Greg KH <greg@kroah.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
mochel@osdl.org, "Moore, Eric Dean" <Eric.Moore@lsil.com>,
"Patterson, Andrew D (Linux R&D)" <andrew.patterson@hp.com>,
Luben Tuikov <luben_tuikov@adaptec.com>
Subject: Re: 2.6: how do I this in sysfs?
Date: Mon, 29 Aug 2005 15:32:11 -0700 [thread overview]
Message-ID: <20050829223211.GA17088@kroah.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF10ABB0269@cceexc23.americas.cpqcorp.net>
On Mon, Aug 29, 2005 at 12:24:18PM -0500, Miller, Mike (OS Dev) wrote:
>
> > This is after my minimal sas transport class, please also
> > read the thread about it on linux-scsi
> >
> In the referenced code for using sysfs, there only appear to be methods
> for reading attributes. How about if we want to cause a command to
> get written out to the hardware? Do we do something like this?
>
> /* get a semaphore keep everyone else out while we're working,
> and hope like hell that all the other processes are playing
> nice and using the semaphore too, or else we're hosed. */
>
> get_some_kind_of_semaphore();
try flock() on the /sys/blah/blah/ directory. That should keep userspace happy.
I think it only takes a small sysfs patch to make this work (or it might work
today, don't remember, sorry...)
Or look into using configfs instead.
thanks,
greg k-h
next prev parent reply other threads:[~2005-08-29 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 17:24 2.6: how do I this in sysfs? Miller, Mike (OS Dev)
2005-08-29 17:24 ` Miller, Mike (OS Dev)
2005-08-29 22:32 ` Greg KH [this message]
2005-08-29 23:17 ` gcoady
2005-08-29 23:17 ` gcoady
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 18:52 Miller, Mike (OS Dev)
2005-08-25 18:52 ` Miller, Mike (OS Dev)
2005-08-25 19:02 ` Andrew Patterson
2005-08-25 19:09 ` Christoph Hellwig
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=20050829223211.GA17088@kroah.com \
--to=greg@kroah.com \
--cc=Eric.Moore@lsil.com \
--cc=Mike.Miller@hp.com \
--cc=andrew.patterson@hp.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=mochel@osdl.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 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.