From: Matthew Wilcox <matthew@wil.cx>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com, Eric.Moore@lsi.com,
Sathya.Prakash@lsi.com
Subject: Re: [PATCH 1/3] mpt2sas: removetheuseofwriteq@lsi.com, since writeq is not atomic
Date: Wed, 4 May 2011 13:42:20 -0600 [thread overview]
Message-ID: <20110504194220.GA25875@parisc-linux.org> (raw)
In-Reply-To: <20110504110317.GA17855@lsi.com>
On Wed, May 04, 2011 at 04:33:51PM +0530, Kashyap, Desai wrote:
> We need the 64 bit completed in one access pci memory write, else spin lock is required.
> Since it's going to be difficult to know which writeq was implemented in the kernel,
> the driver is going to have to always acquire a spin lock each time we do 64bit write.
> */
> -#ifndef writeq
> static inline void _base_writeq(__u64 b, volatile void __iomem *addr,
> spinlock_t *writeq_lock)
> {
> @@ -1570,13 +1569,6 @@ static inline void _base_writeq(__u64 b, volatile void __iomem *addr,
> writel((u32)(data_out >> 32), (addr + 4));
> spin_unlock_irqrestore(writeq_lock, flags);
> }
> -#else
> -static inline void _base_writeq(__u64 b, volatile void __iomem *addr,
> - spinlock_t *writeq_lock)
> -{
> - writeq(cpu_to_le64(b), addr);
> -}
> -#endif
>
Instead of taking out this optimisation (which is going to hurt massively
on 8-socket systems), why not simply change:
-#ifndef writeq
+#if BITS_PER_LONG < 64
(OK, there's an assumption that all 64-bit systems have an atomic 64-bit
MMIO store operation ... but I think that's a valid assumption).
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2011-05-04 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 11:03 [PATCH 1/3] mpt2sas: removetheuseofwriteq@lsi.com, since writeq is not atomic Kashyap, Desai
2011-05-04 11:32 ` Desai, Kashyap
2011-05-04 19:42 ` Matthew Wilcox [this message]
2011-05-05 6:59 ` Desai, Kashyap
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=20110504194220.GA25875@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Sathya.Prakash@lsi.com \
--cc=kashyap.desai@lsi.com \
--cc=linux-scsi@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