From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-arch@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [RFC] Implement dma_boundary in the generic device
Date: 29 Feb 2004 10:52:41 -0600 [thread overview]
Message-ID: <1078073562.1756.46.camel@mulgrave> (raw)
In-Reply-To: <20040229164630.GH25779@parcelfarce.linux.theplanet.co.uk>
On Sun, 2004-02-29 at 10:46, Matthew Wilcox wrote:
> <nitpick style=janitor> Space between "if" and "(" </nitpick>
Well, I think I've already proved I'm not a very good janitor with the
attempt to shift coherent_dma_mask ...
> Don't all architectures want a limit to 4GB boundaries, to avoid crossing
> the first 4GB?
That is the fundamental limit, that's why I set it up to 4GB at
initialisation. I anticipate that if platforms want to enforce an upper
bound, they would override dma_set_boundary().
James
next prev parent reply other threads:[~2004-02-29 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 15:56 [RFC] Implement dma_boundary in the generic device James Bottomley
2004-02-29 16:46 ` Matthew Wilcox
2004-02-29 16:52 ` James Bottomley [this message]
2004-03-01 11:46 ` 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=1078073562.1756.46.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linux-arch@vger.kernel.org \
--cc=willy@debian.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