On Fri, Jan 14, 2011 at 01:26:33PM -0800, Roland Dreier wrote: > > > Regardless of whether what I say above is correct or not, wouldn't it > > > be nicer to to define pfn as either u64 or phys_addr_t and avoid the > > > casting? > > > > Good point, the pfn must be stored as phys_addr_t too, otherwise you > > only support a 44 bit physical address space before truncatation > > occures. > > Not sure I agree at the moment... eg remap_pfn_range takes unsigned > long. So I don't think things will really work on a 32-bit arch with > > 44 bit bus addresses for lots of other reasons.
Hmm, fair point. It does look to me like pfns are generally (always?) stored as unsigned long, so there is no attempt to support more physical bits than about 44 or so on 32 bit. But I also don't know of any places that actually check for this when processing BARs... :) Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
