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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <48D09BC2.1040704@manoweb.com>
Date:	Tue, 16 Sep 2008 22:55:14 -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:

> Would it be more of a performance win to use the 8-32K to store speed-critical
> code rather than a FIFO?  Just another idea for what to use it for, but that
> would likely require a different API...

Well... I have to check but I think the cache memory is anyway faster
than this, and this memory is not cacheable. But, you definitely have a
point. I'll check with some hardware guy tomorrow morning.

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/