From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/5] percpu_counter: modifications to __percpu_counter_add_unless_lt()
Date: Wed, 22 Dec 2010 21:56:07 -0600 [thread overview]
Message-ID: <1293076567.2408.424.camel@doink> (raw)
This series is based on (i.e., applies on top of)
the third patch in Dave Chinner's scalability series
(lib: percpu counter add unless less than functionality).
I had some questions while reviewing that patch, and
after closer inspection I think I found what I think
are some problems, and in order to work through them
I came up with this patch series to lay out what I
think the problems are and my attempt at addressing
them.
The series has been rearranged a bit since I put it
together. Patch 3 includes some background and
terminology that might be more useful at the
beginning, but I'm leaving it as-is for now.
The more I look at the end result of the series the
more confident I am that it's correct. However I
still need some convincing--either to point out
where I've got something wrong, or to affirm that
what I have is right.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2010-12-23 3:56 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=1293076567.2408.424.camel@doink \
--to=aelder@sgi.com \
--cc=xfs@oss.sgi.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.