Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <6b52ae5515072186f125783ca8493721@www.novabbs.org>
Deutsch   English   Français   Italiano  
<6b52ae5515072186f125783ca8493721@www.novabbs.org>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: mitchalsup@aol.com (MitchAlsup1)
Newsgroups: comp.arch
Subject: Re: PCIe MSI-X interrupts
Date: Fri, 28 Jun 2024 20:26:42 +0000
Organization: Rocksolid Light
Message-ID: <6b52ae5515072186f125783ca8493721@www.novabbs.org>
References: <bb16865f7675526d4e2b87283e28c2c5@www.novabbs.org> <sKmdO.62321$G9_a.28048@fx13.iad> <bejeO.24905$Gurd.6236@fx34.iad> <8JkeO.30075$WaKd.3069@fx41.iad> <f9e2c222349934ce0d6d9cda5b55f8b7@www.novabbs.org> <FNzeO.141608$Cqra.114681@fx10.iad> <09dac1eb164a4c5226036cbde84884da@www.novabbs.org> <20240627112720.00005063@yahoo.com> <%LdfO.108407$xKj1.7795@fx09.iad> <ecd43e7ed4d3cc6fcc3bca3a999725e8@www.novabbs.org> <0vBfO.55376$J8n7.6978@fx12.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="1505847"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A";
User-Agent: Rocksolid Light
X-Rslight-Site: $2y$10$VHsjVnoremRyXM1G/p0F.esFMARAsawBVJQvueoIjYTLAZqXoa/oK
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8
Bytes: 2502
Lines: 29

EricP wrote:

> MitchAlsup1 wrote:

>> Sounds like SNARFing

> Write-update depends on broadcasting all writes if that's what snarf
> means.

General cache coherency policies broadcast a cores address to all
caches in the system, and if that cache contains that same cache
line, it responds with a SHARED back to requestor, or it invalidates
the line. We call this SNOOPing. It works well.

SNARF is a term whereby the owner of data broadcasts the data and
its address, and any cache containing that line will write the
data payload into its cache 9rather than invalidating and then
going back and fetching it anew. For certain kinds of data struct
SNARF is significantly more efficient than Invalidate-Refetch.
A single message around the system performs all the needed updates,
instead of 1 invalidate and K fetches.

SNARF is almost exclusively used as side-band signals hiding under
the cache coherent Interconnect command set.

SNARF is almost never available to software. It is more like micro-
Architecture talking to other microArchitecture.

Also note: µA-to-µA is rarely of line size and often uses physical
address bits not available through MMU tables.