From: Mike Christie <michaelc@cs.wisc.edu>
To: paulmck@us.ibm.com
Cc: stelian@popies.net, linux-kernel@vger.kernel.org, akpm@osdl.org,
paulus@au1.ibm.com, anton@au1.ibm.com,
open-iscsi@googlegroups.com, pradeep@us.ibm.com,
mashirle@us.ibm.com
Subject: Re: [PATCH] memory ordering in __kfifo primitives
Date: Thu, 10 Aug 2006 01:48:02 -0400 [thread overview]
Message-ID: <44DAC892.7000100@cs.wisc.edu> (raw)
In-Reply-To: <20060810003310.GA3071@us.ibm.com>
Paul E. McKenney wrote:
> OK, it appears that we are even. I forgot to attach the promised
> analysis of the callers to __kfifo_put() and __kfifo_get(), and
> the open-iscsi@googlegroups.com email address listed as maintainer
> in drivers/scsi/libiscsi.c bounces complaining that, as a non-member,
> I am not allowed to send it email. ;-)
Sorry about that. I do not have any control over the email list. I will
change the maintainer info entry to indicate that users should just send
mail to me or linux-scsi.
>
> Anyway, this time the analysis really is attached, sorry for my confusion!
>
We have change the code a little since the analysis was made. But, it
does not really matter much now. I am fine with us just grabbing the
session lock or xmitmitex (I will send a patch and test it as well) if
your barrier patch is not accepted. We grab the session lock in the fast
path now so there is not much benefit left for us.
next prev parent reply other threads:[~2006-08-10 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 0:18 [PATCH] memory ordering in __kfifo primitives Paul E. McKenney
2006-08-10 0:29 ` Andrew Morton
2006-08-10 1:01 ` Paul E. McKenney
2006-08-10 0:33 ` Paul E. McKenney
2006-08-10 5:48 ` Mike Christie [this message]
2006-08-10 13:41 ` Paul E. McKenney
2006-08-10 14:26 ` Stelian Pop
2006-08-10 15:39 ` Paul E. McKenney
2006-08-10 15:47 ` Stelian Pop
2006-08-10 16:11 ` Paul E. McKenney
2006-08-10 16:23 ` Stelian Pop
2006-08-10 16:47 ` Paul E. McKenney
2006-08-10 20:27 ` Stelian Pop
2006-08-10 20:54 ` Paul E. McKenney
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=44DAC892.7000100@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=akpm@osdl.org \
--cc=anton@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=open-iscsi@googlegroups.com \
--cc=paulmck@us.ibm.com \
--cc=paulus@au1.ibm.com \
--cc=pradeep@us.ibm.com \
--cc=stelian@popies.net \
/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