linux-kernel - Re: Driver for tightly coupled memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48D0954D.4070302@manoweb.com>
Date:	Tue, 16 Sep 2008 22:27:41 -0700
From:	Alessio Sangalli <alesan@...oweb.com>
To:	Valdis.Kletnieks@...edu
CC:	Ben Nizette <bn@...sdigital.com>, Ben Dooks <ben-linux@...ff.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Driver for tightly coupled memory

Valdis.Kletnieks@...edu wrote:

> What sort of hardware/software interface does the TCM provide?  You mentioned
> that it could be accessed even while main memory is being accessed - what does
> that look like from the software level?

Well I should ask the details to the hardware engineers but it's like a
separate channel than the one used for main memory. It is not cacheable
either. To the CPU, it just appears to be mapped at some location on the
addressable space. Accessing this TCM will not have any impact on main
memory access, so bursts etc won't be interrupted; other than that, TCM
has double the bandwidth than standard memory - but it's tiny in size,
something like 8 to 32kB as I mentioned earlier.

Hope I was clear enough, feel free to ask me more details if you need

bye
as

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/