From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <608b86015aa017ae148c654b8314dbe1@plug.quanstro.net> References: <608b86015aa017ae148c654b8314dbe1@plug.quanstro.net> Date: Tue, 28 Dec 2010 11:41:30 +0100 Message-ID: From: Gorka Guardiola To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] dumb kw question Topicbox-Message-UUID: 8e5e43d2-ead6-11e9-9d60-3106f5b1d025 On Mon, Dec 27, 2010 at 3:00 PM, erik quanstrom wro= te: > On Mon Dec 27 04:07:57 EST 2010, 9fans@hamnavoe.com wrote: >> > what does BY2SE stand for? >> > bytes per what? >> >> I don't know the answer but here's a clue: >> >> ether1116.c:573: =A0 =A0 =A0 =A0 =A0 =A0 =A0cachedwbse(&r->cs, BY2SE); >> >> l.s:342: TEXT cachedwbse(SB), 1, $-4 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= /* D writeback SE */ > > after quite the go around, BY2SE stands for "single entry". > which begs the question "single entry" of what. =A0it appears > that it means a cache line, which is 32 bytes, judging from the > rounding that both l2cacheuwbse and cachedwbse do, all > the cachelines covered by the given object are flushed. > > if i'm reading the code correctly, ... > - shouldn't BY2SE be replaced by either BY2WD or sizeof(thing)? > Se is in fact single entry in the cache, i.e. cache line. It is not a word necessarily (on other arm arquitectures it is 64 bytes if I remember right) and it is used in assembly so a define is the way to go. G.