>> I don't think the proposed 32-bit behavior is off the mark, and
>> anyways x86 can actually make the 64-bit store I believe if it
>> wants at least on more recent processors.
Surely we wouldn't want to define a new API that can't be supported on
all 32-bit platforms, no? Perhaps writeq_nonatomic()?
I'm saying we define writeq() to be implementable as two 32-bit
transations, that will be the API.
I think adding some weird new writeq_nonatomic() will just create
more confusion than it saves.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/