From: Matt Porter <mporter@kernel.crashing.org>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: Matt Porter <mporter@kernel.crashing.org>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: [RFC] consistent_sync and non L1 cache line aligned buffers
Date: Tue, 15 Jul 2003 16:51:16 -0700 [thread overview]
Message-ID: <20030715165116.B8616@home.com> (raw)
In-Reply-To: <5.1.0.14.2.20030715092123.02ef0d20@mail.ebshome.net>; from ebs@ebshome.net on Tue, Jul 15, 2003 at 09:27:10AM -0700
On Tue, Jul 15, 2003 at 09:27:10AM -0700, Eugene Surovegin wrote:
>
> At 09:17 AM 7/15/2003, Matt Porter wrote:
> >I'll agree that it's a better hack, but since the offending areas in
> >the SCSI subsystem are easily located, it seems wiser to fix upstream.
>
> Matt, the problem is it wasn't that *easy* to locate this, at least for me :)
> I'm not sure that this is the only place..
I didn't mean to trivialize the difficulty of finding this from the path
of tracking the symptom to the source. :) I merely was pointing out
that now that you know the source of the problem, it's not *too* difficult
to look for buffers allocated on the stack by simple inspection of the
SCSI code. I only jumped in on this because I felt a little guilty that
when I noticed this sometime back I got distracted and never tried to
send a patch to the maintainers. :-/
> >We still need someone with interest AND time to properly fix the
> >consistent alloc from irq issue. :) All of the patches post to date
> >are incomplete bandaids.
>
> Uhh, I switched to solution which uses pre allocated consistent memory (10
> pages are enough for sym53c8xx_2).
> It's still not a generic solution, but at least it's safe :)
Are you doing this in the sym_2 driver or in the ppc consistent_*
implementations? I only ask because I finally convinced myself
recently that attempting to make all the locking safe in the VM
subsystem was too much work. I think Paul suggested at one point
that we might just preallocate a pool for atomic consistent allocations
anyway.
Regards,
--
Matt Porter
mporter@kernel.crashing.org
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-15 23:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 4:32 [RFC] consistent_sync and non L1 cache line aligned buffers Eugene Surovegin
2003-07-15 15:46 ` Tom Rini
2003-07-15 16:20 ` Eugene Surovegin
2003-07-15 16:25 ` Tom Rini
2003-07-15 16:17 ` Matt Porter
2003-07-15 16:27 ` Eugene Surovegin
2003-07-15 18:11 ` PPCBoot on Ebony board Brian Padalino
2003-07-15 21:32 ` Chris Zimman
2003-07-16 11:59 ` Brian Padalino
2003-07-16 14:29 ` Chris Zimman
2003-07-16 15:39 ` Brian Padalino
2003-07-16 14:45 ` Roland Dreier
2003-07-15 23:51 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 20:18 [RFC] consistent_sync and non L1 cache line aligned buffers Darin.Johnson
[not found] <F0B628F30F48064289D8CCC1EE21B7A80C48A5@mvebe001.americas.n okia.com>
2003-07-15 20:39 ` Eugene Surovegin
2003-07-15 21:26 ` David Blythe
2003-07-15 22:15 ` Dan Malek
2003-07-15 20:47 Darin.Johnson
2003-07-15 23:04 Darin.Johnson
2003-07-15 23:34 ` Paul Mackerras
2003-07-15 23:50 ` Eugene Surovegin
2003-07-15 23:45 ` Matt Porter
2003-07-16 14:01 ` Dan Malek
2003-07-16 0:12 Darin.Johnson
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=20030715165116.B8616@home.com \
--to=mporter@kernel.crashing.org \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.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).