From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dumb kw question
Date: Tue, 28 Dec 2010 08:59:23 -0500 [thread overview]
Message-ID: <1f96d8452adeb9a72bb1a9972140fc18@plug.quanstro.net> (raw)
In-Reply-To: <AANLkTiksB4XMHkHrFcE_7TQ_y138-g8ibvEqsjShyHiK@mail.gmail.com>
> > On Mon, Dec 27, 2010 at 3:00 PM, erik quanstrom <quanstro@quanstro.net> wro
>
> >
> > Se is in fact single entry in the cache, i.e. cache line. It is not a word
> > necessarily (on other arm architectures it is 64 bytes if I remember right)
> > and it is used in assembly so a define is the way to go.
> >
>
> I mean other arm processors, same architecture.
i think you misunderstand what i'm saying. i don't care that its a define,
i suspect that the definition makes no sense, and calling
cache lines "single entries" is obtuse, even for kernel
assembly code. :-)
at least my copy of the kw code has
BY2SE = 4,
CACHELINESZ = 32, ( verified by kw l2 cache doc )
i would think that BY2SE would need to be the
same as CACHELINESZ, so BY2SE is incorrect
and redundant.
regardless, the *se(base, sz) functions don't clear a single entry
they clear all cache lines intersecting
[base & ~(CACHELINESZ-1), base+size)
so the second argument really should be the size of the object
that needs to be flushed from cache.
to me it would make sense remove BY2SE and replace with
BY2WD, since its always used to indicated the object to be flushed
is word-sized. and replace *se(base, sz) with *cls(base, sz) or
*entries(base, sz).
- erik
next prev parent reply other threads:[~2010-12-28 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 2:52 erik quanstrom
2010-12-27 9:06 ` Richard Miller
2010-12-27 14:00 ` erik quanstrom
2010-12-28 10:41 ` Gorka Guardiola
2010-12-28 10:42 ` Gorka Guardiola
2010-12-28 13:59 ` erik quanstrom [this message]
2010-12-30 1:05 ` Charles Forsyth
2010-12-30 1:24 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f96d8452adeb9a72bb1a9972140fc18@plug.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).