From: Roopesh <roopesh@cyberspace.org>
To: linux-kernel@vger.kernel.org
Subject: Synchronization between VFS and special IO requests to a block device.
Date: Wed, 18 Jan 2006 06:00:22 -0500 [thread overview]
Message-ID: <20060118110022.GA32663@grex.cyberspace.org> (raw)
Hi,
I have an SD card, a partition of which is mounted and is accessed
only through VFS, and certain sectors out of this partition having
some special data which is accessed by the applications only through
certain ioctls to the device.
My problem is in synchronizing/serializing these two accesses to the
hardware, especially since I dont want a VFS request to be handled
by the driver inbetween two specific ioctls. I understand that the
strategy routine should be atomic and that it cant wait on a lock or
sleep. Any pointers/suggestions/help?
Mine is a 2.4 kernel with a uni-processor.
Thanks in Advance,
Roopesh.
PS: Kindly mark a CC: to me if posting. Thanks.
next reply other threads:[~2006-01-18 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 11:00 Roopesh [this message]
2006-01-19 14:57 ` Jan Kara
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=20060118110022.GA32663@grex.cyberspace.org \
--to=roopesh@cyberspace.org \
--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®