From: Matt Porter <mporter@kernel.crashing.org>
To: Darin.Johnson@nokia.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [RFC] consistent_sync and non L1 cache line aligned buffers
Date: Tue, 15 Jul 2003 16:45:58 -0700 [thread overview]
Message-ID: <20030715164557.A8616@home.com> (raw)
In-Reply-To: <F0B628F30F48064289D8CCC1EE21B7A80C48A8@mvebe001.americas.nokia.com>; from Darin.Johnson@nokia.com on Tue, Jul 15, 2003 at 04:04:24PM -0700
On Tue, Jul 15, 2003 at 04:04:24PM -0700, Darin.Johnson@nokia.com wrote:
>
> > IMHO, the easiest solution is
> > alignment of buffers.....plus it's likely to be a performance
> > improvement.
>
> True, it's the easiest solution for the kernel developer, but
> requires more work from driver authors. Which is ok, *if* it's
> well documented and everyone knows buffers must be aligned,
> and that's the problem. I think some people implicitly understand
> these issues, and assume that everyone else thinks the same way.
What more do you expect than the "What memory is DMA'able?" section
in Documentation/DMA-mapping.txt?
It's there to refer the developers to. Some maintainers have bugs
in their drivers/subsystems. They just need a patch from the people
that depend on the bug fix.
I know you are now focusing on some 8xx buffer issue but the original
issue was surrounding generic SCSI subsystem bugs.
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:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 23:04 [RFC] consistent_sync and non L1 cache line aligned buffers Darin.Johnson
2003-07-15 23:34 ` Paul Mackerras
2003-07-15 23:50 ` Eugene Surovegin
2003-07-15 23:45 ` Matt Porter [this message]
2003-07-16 14:01 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 0:12 Darin.Johnson
2003-07-15 20:47 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:18 Darin.Johnson
2003-07-15 4:32 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 23:51 ` Matt Porter
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=20030715164557.A8616@home.com \
--to=mporter@kernel.crashing.org \
--cc=Darin.Johnson@nokia.com \
--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 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.