blocks|key|1165667|text|如果你要深入到某个不知名的芯片中去，那肯定会有助于理解你想要控制的硬件的基本知识。过去，我做过一些控制台渲染器的编程，这基本上是在金属上进行的，这对更高层次的API使用产生了积极的影响。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1165668|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Not if you 're going to dive in to some obscure chip, but it most certainly helps to understand the basics of the hardware you're trying to control. I've done some console renderer programming in the past that was pretty much on the metal and that has positively influenced higher-level API usage.

blocks|key|886577|text|这绝对是一个好主意，有一个坚实的理解，使GPU运行。如果你知道你的卡在一个很深的层次，你可以很容易地识别瓶颈，并获得最大的性能。问题是，找到最新的信息是相当困难的，除非你直接去找制造商，而且他们显然不会告诉你他们的卡是如何工作的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|886578|你发布的链接是一个非常有用的入门，我读过它自己，但请注意日期。它是在2011年发布的，这意味着它已经过时近3年了。在GPU的世界里，3年可能也是一辈子。|886579|这里有几个链接到nvidia和AMD的开发者网站，你可能会在那里找到好的信息。|886580|http://developer.amd.com/|offset|length|886581|https://developer.nvidia.com/|886582|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|P|0|0|0|T|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$H|X|I|Y|1|Z]]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$H|11|I|12|1|13]]|A|$]]|$1|L|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|G]]|S|$5|O|P|Q|A|$R|K]]]]

Its definitely a good idea to have a solid understanding of what makes a GPU tick. If you know your card at a deep level, than you can easily identify bottlenecks and get maximum performance. The trouble is, finding up to date information is pretty difficult, unless you go straight to the manufacturers, and they obviously won't tell you everything about how their card works. 

That link you posted is a really helpful primer, I've read it myself, but take note of the date. It was posted in 2011, which means it is almost 3 years out of date now. In the GPU world, 3 years might as well be a lifetime.

Here's a few links to nvidia and AMD's developer sites, you would probably find good information there.

<a href="http://developer.amd.com/" rel="nofollow">http://developer.amd.com/</a>

<a href="https://developer.nvidia.com/" rel="nofollow">https://developer.nvidia.com/</a>

blocks|key|1165740|text|ARB汇编语言？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1165741|副业编号。|1165742|你不需要知道这一点，虽然许多专业人士已经这样做，因为在行业之前，+GLSL或Cg的存在。老实说，我不能说我对使用ARB汇编语言感到更好，所有相同的概念都是用GLSL教授的。许多应用于ARB+/VP的硬件限制不再有效。|offset|length|style|BOLD|1165743|通过学习它，你可能会对自己造成损害，比如学习即时模式或固定功能管道，它与现代硬件/软件毫无关系。|1165744|​|1165745|也就是说，你链接到的博客是一个非常好的东西去阅读。不要担心硬件指令集(甚至ARB语言实际上也是一个虚拟指令集，稍后由驱动程序翻译成硬件的本地ISA)。相反，您应该理解管道本身。|1165746|1165747|从长远来看，对管道的高级概述会对你有更好的帮助。底层的硬件优化技术随着每一代的变化而变化，但是管道的基本阶段仍然是相对静态的(当然，新的可编程阶段是定期引入的)。如果您从高层次了解管道，那么您将准备学习并应用新的硬件特性。|1165748|entityMap^0|0|0|T|3|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@$F|X|G|Y|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|11|8|@]|9|@]|A|$]]|$1|P|3|M|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

ARB assembly language?

<h3>&nbsp;&nbsp;&nbsp;No.</h3>

You do not need to know that, though many professionals already do as a consequence of being in the industry before GLSL or Cg existed. To be honest, I cannot say that I feel any better off having experience with the ARB assembly language, all of the same concepts are taught in GLSL. And many of the hardware restrictions that applied to ARB FP/VP are no longer valid.

You would probably be doing yourself a disservice by learning it, like learning immediate mode or the fixed-function pipeline, it simply is not relevant to modern hardware/software.

<hr>
That said, the blog you linked to is a very good thing to read. Do not concern yourself with hardware instruction sets (even the ARB languages are actually a virtual instruction set, translated by the driver later into the hardware's native ISA). Instead, you should understand the pipeline itself.

A high-level overview of the pipeline will do you better in the long-run. Underlying hardware optimization techniques change with each generation, but the fundamental stages of the pipeline remain relatively static (of course new programmable stages are periodically introduced). If you understand the pipeline from a high-level, then you will be prepared to learn about and apply new hardware features as they are introduced.

e.g. If I learn the low-level <a href="http://fgiesen.wordpress.com/2011/07/01/a-trip-through-the-graphics-pipeline-2011-part-1/" rel="nofollow">Graphics Pipeline</a>, take a trip on learning the ARB assembly language and understand the logic for certain gpu device driver calls can it help me enhance my knowledge in GPU API programming or is there no correlation whatsover and will I be only wasting my time? 

EDIT: Do professionals need to understand this to a degree?

Can understanding the low-level intricacies of a GPU/core-drivers develop your skill with working with Graphic APIs?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

例如，如果我学习低水平的，就学习ARB汇编语言，了解某些gpu设备驱动程序调用的逻辑，它能帮助我提高我在GPU编程方面的知识吗?或者没有关联，我会浪费时间吗？编辑:专业人士需要在一定程度上理解这一点吗？

问理解GPU/核心驱动程序的低层次复杂之处能提高您使用图形API的技能吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问理解GPU/核心驱动程序的低层次复杂之处能提高您使用图形API的技能吗？EN