From: Daniel McNeil <daniel@osdl.org>
To: Andrew Morton <akpm@digeo.com>, Andrea Arcangeli <andrea@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.5.68 1/2] i_size atomic access
Date: 24 Apr 2003 17:20:56 -0700 [thread overview]
Message-ID: <1051230054.2448.14.camel@ibm-c.pdx.osdl.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
This adds a sequence counter only version of the reader/writer
consistent mechanism to seqlock.h This is used in the second
part of this patch give atomic access to i_size.
re-diff against 2.5.68.
The patch is also available for download from OSDL's patch lifecycle
manager (PLM):
http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1801
Thanks,
--
Daniel McNeil <daniel@osdl.org>
[-- Attachment #2: patch-2.5.68-isize.1 --]
[-- Type: text/x-troff-man, Size: 1487 bytes --]
--- linux-2.5.68/include/linux/seqlock.h Sat Apr 19 19:49:23 2003
+++ linux-2.5.68-isize/include/linux/seqlock.h Thu Apr 24 14:30:57 2003
@@ -94,6 +94,57 @@ static inline int read_seqretry(const se
return (iv & 1) | (sl->sequence ^ iv);
}
+
+/*
+ * Version using sequence counter only.
+ * This can be used when code has its own mutex protecting the
+ * updating starting before the write_seqcntbeqin() and ending
+ * after the write_seqcntend().
+ */
+
+typedef struct seqcnt {
+ unsigned sequence;
+} seqcnt_t;
+
+#define SEQCNT_ZERO { 0 }
+#define seqcnt_init(x) do { *(x) = (seqcnt_t) SEQCNT_ZERO; } while (0)
+
+/* Start of read using pointer to a sequence counter only. */
+static inline unsigned read_seqcntbegin(const seqcnt_t *s)
+{
+ unsigned ret = s->sequence;
+ smp_rmb();
+ return ret;
+}
+
+/* Test if reader processed invalid data.
+ * Equivalent to: iv is odd or sequence number has changed.
+ * (iv & 1) || (*s != iv)
+ * Using xor saves one conditional branch.
+ */
+static inline int read_seqcntretry(const seqcnt_t *s, unsigned iv)
+{
+ smp_rmb();
+ return (iv & 1) | (s->sequence ^ iv);
+}
+
+
+/*
+ * Sequence counter only version assumes that callers are using their
+ * own mutexing.
+ */
+static inline void write_seqcntbegin(seqcnt_t *s)
+{
+ s->sequence++;
+ smp_wmb();
+}
+
+static inline void write_seqcntend(seqcnt_t *s)
+{
+ smp_wmb();
+ s->sequence++;
+}
+
/*
* Possible sw/hw IRQ protected versions of the interfaces.
*/
reply other threads:[~2003-04-25 0:11 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=1051230054.2448.14.camel@ibm-c.pdx.osdl.net \
--to=daniel@osdl.org \
--cc=akpm@digeo.com \
--cc=andrea@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).