From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
rmk@arm.linux.org.uk
Subject: Re: SCSI breakage on non-cache coherent architectures
Date: Mon, 19 Nov 2007 00:38:02 -0800 (PST) [thread overview]
Message-ID: <20071119.003802.100741794.davem@davemloft.net> (raw)
In-Reply-To: <1195450523.7022.37.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Mon, 19 Nov 2007 16:35:23 +1100
> I'm not sure what is the best way to fix that. Internally, I've done
> some test whacking some ____cacheline_aligned in the scsi_cmnd data
> structure to verify I no longer get random SLAB corruption when using my
> USB but that significantly bloats the size of the structure on archs
> such as ppc64 that don't need it and have a large cache line size.
>
> Unfortunately, I don't think there's any existing Kconfig symbol or arch
> provided #define to tell us that we are on a non-coherent arch afaik
> that could be used to make that conditional.
>
> Another option would be to kmalloc the buffer (wasn't it the case before
> btw ?) but I suppose some people will scream at the idea due to how the
> command pools are done...
You could make a ____dma_cacheline_aligned and use that.
It seems pretty reasonable.
next prev parent reply other threads:[~2007-11-19 8:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 5:35 SCSI breakage on non-cache coherent architectures Benjamin Herrenschmidt
2007-11-19 8:38 ` David Miller [this message]
2007-11-19 19:51 ` Benjamin Herrenschmidt
2007-11-19 22:31 ` David Miller
2007-11-20 0:34 ` Benjamin Herrenschmidt
2007-11-20 0:46 ` David Miller
2007-11-20 0:55 ` Benjamin Herrenschmidt
2007-11-20 0:57 ` David Miller
2007-11-20 2:10 ` Roland Dreier
2007-11-20 2:35 ` Benjamin Herrenschmidt
2007-11-20 3:14 ` Benjamin Herrenschmidt
2007-11-20 19:35 ` James Bottomley
2007-11-20 8:29 ` Thomas Bogendoerfer
2007-11-20 14:36 ` James Bottomley
2007-11-20 20:05 ` Roland Dreier
2007-11-20 21:10 ` James Bottomley
2007-11-20 22:39 ` Benjamin Herrenschmidt
2007-11-20 23:09 ` James Bottomley
2007-11-19 12:32 ` Matthew Wilcox
2007-11-19 15:09 ` James Bottomley
2007-11-19 19:54 ` Benjamin Herrenschmidt
2007-11-19 19:55 ` Benjamin Herrenschmidt
2007-11-19 19:53 ` Benjamin Herrenschmidt
2007-11-19 21:43 ` Roland Dreier
2007-11-19 21:55 ` Benjamin Herrenschmidt
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=20071119.003802.100741794.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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