From: David Miller <davem@davemloft.net>
To: arnd@arndb.de
Cc: geert.uytterhoeven@gmail.com, michal.simek@petalogix.com,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: Removing __kernel_old_uid_t, git_t, dev_t
Date: Mon, 30 Mar 2009 14:11:56 -0700 (PDT) [thread overview]
Message-ID: <20090330.141156.62568451.davem@davemloft.net> (raw)
In-Reply-To: <200903301717.57184.arnd@arndb.de>
From: Arnd Bergmann <arnd@arndb.de>
Date: Mon, 30 Mar 2009 17:17:56 +0200
> dma_addr_t is a big mess that was traditionally defined per
> architecture, in lots of wrong ways, including the misconception
> of dma64_addr_t. Sparc64 still uses a 32 bit dma_addr_t, possibly
> because it always uses an IOMMU (?). It can save some space in
> scatterlists, but might come back to bite us if someone tries
> to build a sparc64 system with actual 64-bit DMA.
There is no reason to use anything larger than a 32-bit DMA address
type on sparc64, and using 32-bit saves lots of space in many
data structures so I am unlikely to ever change this. :-)
next prev parent reply other threads:[~2009-03-30 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 7:15 Michal Simek
2009-03-30 13:58 ` Arnd Bergmann
2009-03-30 14:41 ` Geert Uytterhoeven
2009-03-30 15:17 ` Arnd Bergmann
2009-03-30 21:11 ` David Miller [this message]
2009-03-31 0:26 ` Arnd Bergmann
2009-04-01 14:11 ` [RFC] asm-generic/{unistd,types,posix_types}.h for new arch Arnd Bergmann
2009-04-01 14:39 ` Will Newton
2009-04-01 15:04 ` Arnd Bergmann
2009-04-01 21:20 ` H. Peter Anvin
2009-04-01 21:32 ` Roland McGrath
2009-04-02 13:06 ` Arnd Bergmann
2009-04-01 17:55 ` Arnd Bergmann
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=20090330.141156.62568451.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=geert.uytterhoeven@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@petalogix.com \
/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
Powered by JetHome