memcpy_toio on i386 using byte writes even when n%2==0
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · H. Peter Anvin
For something that generates I/O transactions, it's imperative to generate the smallest possible number of transactions. Furthermore, smaller than dword transactions aren't burstable, except at the beginning and end of a burst.
Well, theoretically for writes they could be, if the memory region was prefetchable and the PCI chipset supported byte merge. It certainly isn't optimal however.
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
Quoted 8 lines · Robert Hancock
Quoted 4 lines · H. Peter Anvin
For something that generates I/O transactions, it's imperative to generate the smallest possible number of transactions. Furthermore, smaller than dword transactions aren't burstable, except at the beginning and end of a burst.
Well, theoretically for writes they could be, if the memory region was prefetchable and the PCI chipset supported byte merge. It certainly isn't optimal however.
If so, then merging doesn't matter either way.
-hpa