From: Dhruv Matani <dhruvbird@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: A question about Byte range locking.
Date: Sun, 20 Dec 2009 17:52:23 +0530 [thread overview]
Message-ID: <3a9148b90912200422j1b0b008dp90d0e0cd44ccf31d@mail.gmail.com> (raw)
Hello,
I was reading the kernel code to try and figure out how byte range
locking is implemented inside the kernel, and it looks as if it is
implemented using linked lists of locks which store the range locked
and the type of lock. Am I right??
--
-Dhruv Matani.
http://www.geocities.com/dhruvbird/
"How do you know when someone's crazy?"
"Well, you don't always. Depends on how many people think they're crazy."
-- Rumble Fish.
reply other threads:[~2009-12-20 12:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3a9148b90912200422j1b0b008dp90d0e0cd44ccf31d@mail.gmail.com \
--to=dhruvbird@gmail.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®