From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Robert Mueller <robm@fastmail.fm>, Andrew Morton <akpm@osdl.org>,
rdunlap@xenotime.net, hch@infradead.org, erich@areca.com.tw,
brong@fastmail.fm, dax@gurulabs.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Areca driver recap + status
Date: Tue, 27 Jun 2006 16:51:40 +0100 [thread overview]
Message-ID: <1151423500.32186.39.camel@localhost.localdomain> (raw)
In-Reply-To: <1151422074.3340.25.camel@mulgrave.il.steeleye.com>
Ar Maw, 2006-06-27 am 10:27 -0500, ysgrifennodd James Bottomley:
> On a PAE platform, dma_addr_t is u64 and unsigned long is u32, so any
> address > 4GB will be truncated by these operations.
>
> I think all this does is cause a slow leak of dma mappings, and on any
> kernel > 2.6.16 the leak should be even smaller, since we've severely
> restricted the use_sg == 0 case. It probably is only significant on
> x86_64 with the gart iommu enabled.
On x86_64 the dma_addr_t and the ulong are both 64bit so the problem
doesn't arise.
Alan
next prev parent reply other threads:[~2006-06-27 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 4:18 Areca driver recap + status Robert Mueller
2006-06-22 4:18 ` Robert Mueller
2006-06-22 5:28 ` Andrew Morton
2006-06-22 6:35 ` Jeff Garzik
2006-06-26 14:48 ` James Bottomley
2006-06-26 15:01 ` Andrew Morton
2006-07-07 8:41 ` erich
2006-07-07 8:41 ` erich
2006-07-07 9:04 ` Andrew Morton
2006-06-26 22:32 ` Robert Mueller
2006-06-26 22:32 ` Robert Mueller
2006-06-27 15:27 ` James Bottomley
2006-06-27 15:51 ` Alan Cox [this message]
2006-06-27 15:39 ` James Bottomley
2006-06-27 16:36 ` Alan Cox
2006-06-27 0:23 ` Dax Kelson
2006-06-27 15:27 ` James Bottomley
2006-06-27 9:47 ` erich
2006-06-27 9:47 ` erich
2006-06-27 16:12 ` James Bottomley
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=1151423500.32186.39.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=brong@fastmail.fm \
--cc=dax@gurulabs.com \
--cc=erich@areca.com.tw \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=robm@fastmail.fm \
/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.