BARs are part of the PCI spec, they're the way for firmware and OS to determine the size of the memory or i/o window the card controls as well as the way for the system firmware (usually) to pick what address range the card should use.
In the old days, they were a fixed size. If your GPU has 16 GB of ram and you want to access all of it via memory addresses, you'd need a 16 GB BAR ... but lots of (older) systems wouldn't be able to map in a large BAR because of a lack of address lines (or wahtever), so GPUs had stayed with 256MB for VRAM access because it was compatible. With a smaller BAR than the VRAM, you have to use some sort of windowing / paging setup. Resizable BAR lets the BAR start small so older systems will work, but grow larger with capable systems.
Much better than having a jumper to set the BAR to big or small, and you can skip VRAM window management.
ReBAR stands for "Resizable BAR (Base Address Register)" - it makes the CPU's access window into GPU memory resizable; instead of accessing VRAM in small chunks, the CPU can access much more at once, which can improve performance on some modern GPUs.
i literally don't understand how people move through life - do you expect every single link on this site (or any site) to be ELI5 for you specifically? do you not understand that some things require effort/homework on your part?
What is the purpose of your comments? You failed to answer his question, then attack him for asking the question. Consider the two possibilities: a) doing that homework is easy, b) it's hard. If it's easy, you could have just posted the relevant link and be done. If it's hard, then his question is warranted. Either way, your comments add nothing. One can only conclude that you don't actually know how to answer the question. The real question, though, is: why even bother replying?
Also, ReBAR can get complicated as you can see from other responses above. The articles on the web are also not really good as they tend to replicate marketing material and make vague statements about performance, but fail to explain how specifically performance is improved.
They wanted a basic explanation in response to that.
Or to put it differently, I would take the sentence "He asked for a purpose and a use-case not an explanation." and replace the word "not" with a comma.
Previous classification models need to be trained on the specific question/choices you are trying to output. Jev doesn't need to be retrained for every choice set provided.
LLMs can act as classifiers but they still have to generate text output in the form of a JSON object. This means they have to generate every single curly bracket, quote, command, etc. This turns out to be pretty expensive. On the other hand, Jev uses a different decision head so it doesn't generate text output at all, it outputs logits *only* for the choices provided. So it completely avoids the need to generate text at all, which means no malformed JSON and it's much faster as a result.
Finally, Jev also provides confidence scores that are actually reliable (not made up like LLMs).
Tangentially, since I now write a lot of Zig and there’s no official LSP, I decided to see what life would be without an LSP for all my projects (Go, TS, Python).
Honestly, my LSP requirements are minimal: go to def, find all references, and symbol search. I’ve been wanting to try ctags for awhile and finally made the switch.
Another consideration were all the posts about how grep is better than LSPs for LLMs.
It really pushed me to just get better at grep. There have been a ton of benefits: I can symbol search outside of my editor, it’s much faster than an LSP, minimal configuration. It feels more like a universal tool I can use instead of a tool for IDEs.
emacs has dumb-jump https://github.com/jacktasia/dumb-jump exactly for this, and is often good enough. it uses ripgrep (or some such) for faster-than-grep queries.
It's faster than an lsp?? What on earth are you doing? Even just the context switch to typing the right grep command is slower than ctrl-g or whatever.
As someone who primarily writes in TS, Go, Python, I agree with your assessment: it looks like those languages. The reason I like Go is the reason I like Zig: the language is relatively simple and feels like C.
The C interop is a huge win as someone who wants to do more posix/wayland projects.
I’ve noticed antigravity become significantly slower over the last week or so. It’s a bummer because speed is what I care about. Qwen3.8-27b seems on par with 3.8 flash so if I don’t get speed out of a paid service I’ll just use my local model. Sad.
i think it's better than sonnet 5, especially when you compare speeds. i have to work with the llm anyway, the faster i can turn it the better the outcome.
DNS blocking just isn't as good as a browser extension, because it can only block based on domain names. Pihole helps block ads on non-browser apps, but a real ad blocker extension in a browser is much better. I run pihole on my network, but I still run uBlock Origin on Firefox.
I ran pihole for a while, but I ran into way too many issues with certain sites simply not working at all (booking travel, online shopping...), and it was bothersome to have to constantly allowlist those. UBO works out better.
3 citations and a lot of conjecture. Is the article only targeting SWEs? The one study cited said 22-25 age range saw a 16% decrease in relative employment declines (for SWEs)[0]. But everyone outside that range was not impacted. Further, what about all the trades jobs around data center development?
“Demand is also being intensified by major investments in infrastructure, manufacturing, reshoring, and AI. Data center growth alone has added a net 315,000 skilled-trade workers over the past five years, according to the report, putting additional pressure on an already tight labor market.”
We literally do not have enough trades people to build out data centers and their salaries are increasing as a result. These are skilled labor jobs (plumbers, electricians, IT, etc.). Does Bill Gates care about the rest of the economy outside of SWE?
Honestly a lot of those decreases are also because companies are trying to wait and see as much as possible to see if there is any truth to the conjecture.
I have an impression that most CxO are driven by FOMO. Having a fixed R&D budget (no cheap credit anymore) to get $$$ for tokens they are laying off developers.
What is a BAR let alone a resizable one? Readme just jumps in, which is fine, but I’m not sure why this is on HN or why I should care.
reply