Home / turing-unlock
turing-unlock
WatchingWatchingNone of the above. Nothing stands out yet. More on the methodology pagenlzy/turing-unlock
Unlock full speed FP16 tensor core of NVIDIA Turing GPUs
CCategories: Local AI
Our summary
A Linux kernel module that unlocks the full speed FP16 tensor core of NVIDIA TU102 (Turing) GPUs. It writes two speed selectors and releases an ACR mutex during GPU boot, then returns through the normal Booter finalize path.
Who it is for: Linux users with NVIDIA Turing TU102 GPUs who want to run the FP16 tensor core at full speed
What the README claims
- Tested on the Dell RTX 2080 Ti 22GB with NVIDIA driver 575.51.03
Tested on the Dell RTX 2080 Ti 22GB (`10de:1e07`) with NVIDIA driver 575.51.03.
Not checked - Both the proprietary driver and the open driver work
Both the proprietary driver and the open driver work.
Not checked - Reports a benchmark of cuBALS FP16 matrix multiply with FP32 accumulate on RTX 2080 Ti, with 2048 size rising from 97.9% to 160.6% of peak
TFLOPS of cuBALS FP16 matrix multiply with FP32 Accumulate on RTX 2080 Ti @250W
Not checked - Packages build and install via make targets for Arch, Debian/Ubuntu, and Fedora/RHEL
`make install` finds your distribution. It builds and installs the packages.
Not checked - Module does nothing by default and must be enabled with a kernel command line option
The module does nothing by default. Add one option to the kernel command line:
Not checked
Written by AI from the project's README on 2026-10-27. It does not affect the verdict.
Watching: no other rule matched yet.
7-day star gain 15, up from 9 the week before.
Gaining 15 stars this week. Last push 27 days ago.
Verdict
TOO EARLY scored 1h ago
There is not enough data on this project yet to call it. The numbers below are shown anyway.
Too close to call Hype Gap between -8 and +33.
Early read: we are missing data on the size of the team behind it and how widely it is used. This is an estimate and will be replaced by a verdict once we have the data. How early reads work.
- Hype
- 51
- Reality
- 21
- Hype Gap
- +30
- Momentum
- -
- Confidence
- 60%
- Maintained moves Reality -19 points.
- Responsive moves Reality -4 points.
Rule verdict-2.0, scoring score-2.0. How we score. Backtest.
Maintained by
Maintained by 1 primary developer, 1 external contributor in the last 90 days.
- nlzy is a GitHub individual account.
- GitHub account created April 2015.
- Top contributors by commits: nlzy 50%, coolio986 50%.
Why now 4% of its stars arrived in the last 7 days. No Hacker News posts in the last 7 days.
- Stars StarsThe number of GitHub stars on the repository at our latest reading.
- 374
- Gain 7d Gain 7dStars gained since our latest reading from at least 7 days ago.
- +15
- Pace Velocity (Nx usual pace)This week's star gain divided by the project's usual weekly gain. The usual gain is the average weekly gain over the 4 weeks before (days 8 to 35 ago), counted as at least 10 stars. 2.0x means twice the usual pace. Without a reading from 35 days ago, the ranking assumes 2% of the stars the project had 7 days ago as its usual weekly gain. More on the methodology page
- 1.5x
- HN points HN pointsHacker News points added up across posts that mention the project, published in the last 7 days.
- 0 7 days
- Downloads DownloadsDownloads per day of the project's package, as the registry (npm or PyPI) reports them.
- n/a
- Contributors Contributors, all timePeople and anonymous contributors who have ever committed to the repository, as GitHub counts them. A small number is context, not a flaw: many solid projects are kept by one or two people.
- 2
- Last release Latest releaseDays since the latest GitHub release was published.
- n/a
Gain 24h Gain 24hStars gained since our latest reading from at least 24 hours ago. +1. Forks ForksThe number of GitHub forks of the repository at our latest reading. 60. Open issues Open issuesThe number of open issues on the repository at our latest reading, as GitHub counts them. 29. Days since push Days since pushDays since the last push to the repository. 27 days. Archived ArchivedWhether the owner has archived the repository on GitHub. An archived repository is read-only. no. Hacker News posts in 7 days Hacker News postsThe number of Hacker News posts that mention the project, published in the last 7 days.: 0. Watchers WatchersThe number of GitHub users watching the repository for notifications, at our latest reading. 3.
Facts
Nerd stuff
- Docs
- docs/ folder (detected)
The Receipts
We have stored no threads, mentions, package numbers or dependency facts for this project yet.
What changed recently
GitHub release dates we stored. We do not track license changes yet.
Cite this
turing-unlock is a GitHub project at https://github.com/nlzy/turing-unlock written mainly in C, described there as "Unlock full speed FP16 tensor core of NVIDIA Turing GPUs".
Source: https://midorreal.com/project/nlzy-turing-unlock, checked 22 November 2026. The same facts as JSON: /project/nlzy-turing-unlock.json.
Rank history
Peak day: +42 stars on 27 Oct 2026, 26 days ago.
Stars
Packages
- We checked npm, PyPI, Docker Hub, crates.io and Homebrew and found no package that links to this repository.
Signals
| Source | What we measured | Checked |
|---|---|---|
| GitHub | 374 stars, 15 gained in 7 days | 22 Nov 2026 |
| Hacker News | No posts stored | - |
| Feed mentions | Not tracked yet | - |
| npm | No linked package found | - |
| PyPI | No linked package found | - |
| Docker Hub | No linked package found | - |
| crates.io | No linked package found | - |
| Homebrew | No linked package found | - |
| deps.dev | Not tracked yet | - |
| Hugging Face | Not tracked yet | - |
| Bluesky | Not tracked yet | - |
| Stack Exchange | Not tracked yet | - |
| YouTube | Not tracked yet | - |
Attention vs adoption
Attention: above 75% of tracked projects
Star velocity against all tracked projects
Adoption: not enough data to rank
Downloads, dependents and pulls
Not enough comparable data yet to set attention against adoption. This describes the numbers; it is not a verdict.
Compared with Local AI
| Measure | This project | Category median |
|---|---|---|
| Star velocity | 1.5 | 0.7 |
| Days since release | no data | 8.0 |
| Contributors, all time | 2 | 3 |
| Median time to first reply on issues | no data | 20 hours |
| Commits in the last 30 days | 4 | 31 |
Star velocity: above 76% of Local AI projects
Contributors, all time: above 38% of Local AI projects
Commits in the last 30 days: above 18% of Local AI projects
Compared with the project's first category only. A percentile line appears only where at least 30 projects in the category have the measure. This describes the numbers; it is not a verdict.
Compare with
Hacker News
| Post | Points PointsThe points the post has on Hacker News. | Comments CommentsThe number of comments on the post on Hacker News. | Date |
|---|---|---|---|
| No Hacker News posts mention it in the last 7 days. | |||
Caveats
Repo health
- Languages LanguagesShare of the repository's code by bytes, as GitHub's language detection reports it. The five biggest languages are named and the rest are grouped as Other.C 73%, Python 18%, Makefile 7%, Shell 2%
- License LicenseThe SPDX license id GitHub detects, and a class: Open source (OSI) if the license is on the Open Source Initiative approved list, Source-available if the code is readable but the license limits use, Unclear if GitHub cannot match a known license, No license detected if it finds none. A public repository without a license is not open source.No license detected
- Repository age Repository ageTime since the repository was created on GitHub. This is the repository, not necessarily the project, which may have existed elsewhere before.28 days, created 24 Oct 2026
Development
- Commits in the last 7 days Commits in the last 7 daysCommits to the repository in the last 7 days, as GitHub counts them.0
- Commits in the last 30 days Commits in the last 30 daysCommits to the repository in the last 30 days, as GitHub counts them.4
- Commits in the last 90 days Commits in the last 90 daysCommits to the repository in the last 90 days, as GitHub counts them.4
- Contributors, all time Contributors, all timePeople and anonymous contributors who have ever committed to the repository, as GitHub counts them. A small number is context, not a flaw: many solid projects are kept by one or two people.2, a small team
- Releases ReleasesThe number of GitHub releases, and how many days ago the latest one was published.0
- Issues in the last 30 days Issues in the last 30 daysIssues opened and issues closed in the last 30 days, as GitHub search counts them.27 opened, 1 closed
- Pull requests merged in the last 30 days Pull requests merged in the last 30 daysPull requests merged in the last 30 days, as GitHub search counts them.2
Maintenance
- Median time to close issues Median time to close issuesMedian time from opening to closing, over a sample of the last 30 closed issues.0 hours
- Sampled issues with no reply Sampled issues with no replyHow many of the sampled closed issues never got a comment from someone other than their author.1 of 1
- Stale open issues Stale open issuesOpen issues with no update in the last 90 days, as GitHub search counts them.0
- Open pull requests Open pull requestsPull requests open now, as GitHub search counts them.3
Hygiene
- Automated tests or builds (CI) Automated tests or builds (CI)Whether the repository has at least one GitHub Actions workflow file in .github/workflows.No
- A tests folder A tests folderWhether the repository has a top-level folder named tests, test, __tests__ or spec.No
- A license A licenseWhether GitHub detects a license file in the repository.No
- Contributing guide Contributing guideWhether the repository has a contributing guide.No
- Code of conduct Code of conductWhether GitHub finds a code of conduct in the repository.No
- CODEOWNERS file CODEOWNERS fileWhether the repository has a CODEOWNERS file, which names who reviews changes to which files.No
- A Dockerfile A DockerfileWhether the repository has a Dockerfile at its top level.No
Security
- Security policy Security policyWhether the repository has a SECURITY.md or SECURITY.rst file.No
- Unpatched high or critical advisories Unpatched high or critical advisoriesPublished GitHub security advisories rated high or critical on this repository that list a vulnerable version with no patched version.0
Badge
For maintainers: one measured fact, no verdict.
Markdown
[](https://midorreal.com/project/nlzy-turing-unlock)
HTML
<a href="https://midorreal.com/project/nlzy-turing-unlock"><img src="https://midorreal.com/badge/nlzy-turing-unlock.svg" alt="Mid or Real"></a>
Verdict badge: It shows the verdict as this page shows it today.
Markdown
[](https://midorreal.com/project/nlzy-turing-unlock)
HTML
<a href="https://midorreal.com/project/nlzy-turing-unlock"><img src="https://midorreal.com/badge/nlzy-turing-unlock.svg?style=verdict" alt="Mid or Real: too early"></a>
Passport
Copy these facts into a post, a README or a page. Cite as "Source: Mid or Real". Full record: JSON.
First tracked 26 Oct 2026 at 207 stars.
- GitHub data 72 min old
- Hacker News data 1 min old, no posts found
Is this your project? Claim it
Figures by method 1.0