Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21cde836e531330

Jump to content

Talk:Write combining

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 13 years ago by 2600:1010:B024:ADA5:793D:DF5:D705:F191 in topic Talk

Talk

[edit]

This page is wrong when it says that write combining cannot be used for general memory access because of weak ordering.

It would be correct to say that naive write combining cannot be used, or that making write combining behave in a non-weak ordered fashion requires more complexity.

For example, the Intel P6 used write combining for ordinary WB memory in the special circumstance of "fast strings", REP MOVS and REP STOS. Or perhaps that is what the author would consider special purpose.

Another technique consistent with truly general purpose memory is what I call "left to right write combining": you combine so long as successive writes are exactly adjacent to and monotonically increasing within a cache line. If they are not "left to right", you evict the partial line. AMD's processors have had this for many years.

See http://semipublic.comp-arch.net/wiki/Write_combining#Left_to_right_write_combining

2600:1010:B024:ADA5:793D:DF5:D705:F191 (talk) 06:00, 6 November 2012 (UTC) Andy GlewReply