Searched refs:coe (Results 1 – 5 of 5) sorted by relevance
/Linux-v5.10/tools/memory-model/ |
D | lock.cat | 131 let coe = co & ext
|
D | linux-kernel.cat | 61 empty rmw & (fre ; coe) as atomic
|
/Linux-v5.10/drivers/net/ethernet/smsc/ |
D | smsc9420.c | 1247 u32 coe = smsc9420_reg_read(pd, COE_CR) | RX_COE_EN; in smsc9420_alloc_rx_ring() local 1248 smsc9420_reg_write(pd, COE_CR, coe); in smsc9420_alloc_rx_ring() 1249 netif_dbg(pd, ifup, pd->dev, "COE_CR = 0x%08x\n", coe); in smsc9420_alloc_rx_ring()
|
/Linux-v5.10/tools/memory-model/Documentation/ |
D | explanation.txt | 19 11. CACHE COHERENCE AND THE COHERENCE ORDER RELATION: co, coi, and coe 555 CACHE COHERENCE AND THE COHERENCE ORDER RELATION: co, coi, and coe 674 that occur on different CPUs (external coherence order, or coe). 1177 It's important to understand that neither coe nor fre is included in 1179 W ->coe W'. This means that W and W' are stores to the same location, 1297 The formal definition of the prop relation involves a coe or fre link, 1301 of complexity. For instance, here's an example containing a coe link 1332 overwritten by P1's store since x = 2 at the end (a coe link), the 1357 F via a coe or fre link, an arbitrary number of cumul-fences, an 1362 of links begins with coe). Then there are events W, X, Y, and Z such [all …]
|
/Linux-v5.10/drivers/net/ethernet/stmicro/stmmac/ |
D | stmmac_main.c | 3650 int coe = priv->hw->rx_csum; in stmmac_rx_buf1_len() local 3667 plen = stmmac_get_rx_frame_len(priv, p, coe); in stmmac_rx_buf1_len() 3677 int coe = priv->hw->rx_csum; in stmmac_rx_buf2_len() local 3688 plen = stmmac_get_rx_frame_len(priv, p, coe); in stmmac_rx_buf2_len() 3707 int status = 0, coe = priv->hw->rx_csum; in stmmac_rx() local 3875 if (unlikely(!coe)) in stmmac_rx()
|