blocks|key|1032980|text|module_init()是模块的入口点，在抽象化中，我们对模块进行分层，以便在逻辑上分离功能，提高代码重用等.|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1032981|pci.c为在PCI总线上使用NVMe设备提供了PCI+/+PCIe接口/抽象层？？它与管理有形设备(++)有更多的关系。|unordered-list-item|1032982|nvme_id_table|1032983|nvme_probe()|1032984|nvme_irq()|1032985|1032986|​|1032987|core.c为一般地处理连接到系统的NVMe设备提供了核心驱动程序(它不在乎如何处理)。这个模块更关心的是提供标准化的块设备访问，等等。|1032988|nvme_fops|1032989|nvme_submit_io()|1032990|1032991|1032992|这是整个内核中的一个常见成语，如果一个NVMe设备可以通过另一个总线访问，那么core.c将在没有/最小更改的情况下被重用，并将new_bus.c写到两者之间的接口中。|1032993|如果您使用的是NVMe之上的PCIe，那么希望下面的链能够帮助您理解：|1032994|pci.c实现nvme_pci_reg_read32()|ordered-list-item|1032995|pci.c在nvme_ctrl_ops结构中注册nvme_pci_reg_read32()，名为nvme_pci_ctrl_ops|1032996|core.c实现了nvme_init_ctrl()，它使用指向以下结构之一的指针调用|1032997|结构的core.c+保持引用|1032998|core.c实现了nvme_init_identify()，这需要底层pci.c的帮助。|1032999|core.c通过上述参考资料调用pci.c的nvme_pci_reg_read32()|1033000|如果我们要开发一种支持NVMe设备的新总线，那么我们可以将pci.c替换为new_bus.c，而不对core.c进行任何更改(如前所述)。|1033001|同样值得查看的是Kconfig文件，因为它们可以提示类似的事情--尽管有一定的脑力练习可以通过Makefile将源文件绑定到菜单选项。|1033002|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Abstraction|1|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c|2|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L2095|3|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L1908|4|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L730|5|6|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1054|7|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L673|8|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L1852|9|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L1880|10|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1977|11|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1988|12|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1204|13|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1211|14|https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/Kconfig^0|0|D|M|3|0|0|0|5|0|5|1|1|0|D|0|D|2|1|0|C|0|C|3|1|0|A|0|A|4|1|0|0|0|6|0|6|5|1|0|9|0|9|6|1|0|G|0|G|7|1|0|0|13|6|1S|9|0|0|0|5|7|L|7|L|8|0|0|5|6|D|O|L|1C|H|1C|H|9|0|0|6|9|G|9|G|A|0|3|6|A|4|B|0|0|6|9|K|Z|5|9|K|C|0|0|6|G|5|M|L|8|6|D|0|T|5|11|9|1E|6|0|8|7|1B|8|8|7|E|0^^$0|@$1|2|3|4|5|6|7|2J|8|@$9|2K|A|2L|B|C]]|D|@$9|2M|A|2N|1|2O]]|E|$]]|$1|F|3|G|5|H|7|2P|8|@$9|2Q|A|2R|B|C]]|D|@$9|2S|A|2T|1|2U]]|E|$]]|$1|I|3|J|5|H|7|2V|8|@$9|2W|A|2X|B|C]]|D|@$9|2Y|A|2Z|1|30]]|E|$]]|$1|K|3|L|5|H|7|31|8|@$9|32|A|33|B|C]]|D|@$9|34|A|35|1|36]]|E|$]]|$1|M|3|N|5|H|7|37|8|@$9|38|A|39|B|C]]|D|@$9|3A|A|3B|1|3C]]|E|$]]|$1|O|3|-4|5|6|7|3D|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|3E|8|@]|D|@]|E|$]]|$1|R|3|S|5|H|7|3F|8|@$9|3G|A|3H|B|C]]|D|@$9|3I|A|3J|1|3K]]|E|$]]|$1|T|3|U|5|H|7|3L|8|@$9|3M|A|3N|B|C]]|D|@$9|3O|A|3P|1|3Q]]|E|$]]|$1|V|3|W|5|H|7|3R|8|@$9|3S|A|3T|B|C]]|D|@$9|3U|A|3V|1|3W]]|E|$]]|$1|X|3|-4|5|6|7|3X|8|@]|D|@]|E|$]]|$1|Y|3|Q|5|6|7|3Y|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|3Z|8|@$9|40|A|41|B|C]|$9|42|A|43|B|C]]|D|@]|E|$]]|$1|11|3|12|5|6|7|44|8|@]|D|@]|E|$]]|$1|13|3|14|5|15|7|45|8|@$9|46|A|47|B|C]|$9|48|A|49|B|C]]|D|@$9|4A|A|4B|1|4C]]|E|$]]|$1|16|3|17|5|15|7|4D|8|@$9|4E|A|4F|B|C]|$9|4G|A|4H|B|C]|$9|4I|A|4J|B|C]|$9|4K|A|4L|B|C]]|D|@$9|4M|A|4N|1|4O]]|E|$]]|$1|18|3|19|5|15|7|4P|8|@$9|4Q|A|4R|B|C]|$9|4S|A|4T|B|C]]|D|@$9|4U|A|4V|1|4W]]|E|$]]|$1|1A|3|1B|5|15|7|4X|8|@$9|4Y|A|4Z|B|C]]|D|@$9|50|A|51|1|52]]|E|$]]|$1|1C|3|1D|5|15|7|53|8|@$9|54|A|55|B|C]|$9|56|A|57|B|C]|$9|58|A|59|B|C]]|D|@$9|5A|A|5B|1|5C]]|E|$]]|$1|1E|3|1F|5|15|7|5D|8|@$9|5E|A|5F|B|C]|$9|5G|A|5H|B|C]|$9|5I|A|5J|B|C]]|D|@$9|5K|A|5L|1|5M]]|E|$]]|$1|1G|3|1H|5|6|7|5N|8|@$9|5O|A|5P|B|C]|$9|5Q|A|5R|B|C]|$9|5S|A|5T|B|C]]|D|@]|E|$]]|$1|1I|3|1J|5|6|7|5U|8|@$9|5V|A|5W|B|C]|$9|5X|A|5Y|B|C]]|D|@$9|5Z|A|60|1|61]]|E|$]]|$1|1K|3|-4|5|6|7|62|8|@]|D|@]|E|$]]]|1L|$1M|$5|1N|1O|1P|E|$1Q|1R]]|1S|$5|1N|1O|1P|E|$1Q|1T]]|1U|$5|1N|1O|1P|E|$1Q|1V]]|1W|$5|1N|1O|1P|E|$1Q|1X]]|1Y|$5|1N|1O|1P|E|$1Q|1Z]]|20|$5|1N|1O|1P|E|$1Q|1T]]|21|$5|1N|1O|1P|E|$1Q|22]]|23|$5|1N|1O|1P|E|$1Q|24]]|25|$5|1N|1O|1P|E|$1Q|26]]|27|$5|1N|1O|1P|E|$1Q|28]]|29|$5|1N|1O|1P|E|$1Q|2A]]|2B|$5|1N|1O|1P|E|$1Q|2C]]|2D|$5|1N|1O|1P|E|$1Q|2E]]|2F|$5|1N|1O|1P|E|$1Q|2G]]|2H|$5|1N|1O|1P|E|$1Q|2I]]]]

<code>module_init()</code> is the entry point of a module, and with <a href="https://en.wikipedia.org/wiki/Abstraction" rel="nofollow noreferrer">abstraction</a> we layer the modules to logically separate functionality, improve code reuse, etc...

<ul>
<li><a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c" rel="nofollow noreferrer"><code>pci.c</code></a> provides the PCI / PCIe interface/abstraction layer for using NVMe devices over a PCI bus - it has much more to do with managing tangible devices:

<ul>
<li><a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L2095" rel="nofollow noreferrer"><code>nvme_id_table</code></a></li>
<li><a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L1908" rel="nofollow noreferrer"><code>nvme_probe()</code></a></li>
<li><a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L730" rel="nofollow noreferrer"><code>nvme_irq()</code></a></li>
</ul></li>
<li><a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c" rel="nofollow noreferrer"><code>core.c</code></a> provides the core driver for generically dealing with an NVMe devices connected to the system (it doesn't care how). This module cares more about providing the standardised block device access, etc...

<ul>
<li><a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1054" rel="nofollow noreferrer"><code>nvme_fops</code></a></li>
<li><a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L673" rel="nofollow noreferrer"><code>nvme_submit_io()</code></a></li>
</ul></li>
</ul>

This is a common idiom throughout the kernel, and is done so that if an NVMe device became accessible via another bus, then <code>core.c</code> would be reused with no / minimal changes, and <code>new_bus.c</code> would be written to interface between the two.

<hr>

If you're using NVMe over PCIe, then the following chain will hopefully help things make sense:

<ol>
<li><code>pci.c</code> implements <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L1852" rel="nofollow noreferrer"><code>nvme_pci_reg_read32()</code></a></li>
<li><code>pci.c</code> registers <code>nvme_pci_reg_read32()</code> in the <code>nvme_ctrl_ops</code> structure, named <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/pci.c#L1880" rel="nofollow noreferrer"><code>nvme_pci_ctrl_ops</code></a></li>
<li><code>core.c</code> implements <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1977" rel="nofollow noreferrer"><code>nvme_init_ctrl()</code></a>, which is called with a pointer to one of these structures</li>
<li><code>core.c</code> <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1988" rel="nofollow noreferrer">keeps a reference</a> to the structure</li>
<li><code>core.c</code> implements <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1204" rel="nofollow noreferrer"><code>nvme_init_identify()</code></a>, which needs assistance of the lower-level - <code>pci.c</code></li>
<li><code>core.c</code> calls <code>pci.c</code>'s <code>nvme_pci_reg_read32()</code> via the <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/core.c#L1211" rel="nofollow noreferrer">reference retained above</a></li>
</ol>

If we were to develop a new bus that could support an NVMe device, then we could swap out <code>pci.c</code> for <code>new_bus.c</code> with no changes to <code>core.c</code> (as mentioned above).

<hr>

It's also worth checking out the <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host/Kconfig" rel="nofollow noreferrer"><code>Kconfig</code></a> files as they can hint at things like this - though there is a certain amount of mental gymnastics to tie the source files to the menu options via the <code>Makefile</code>s.

I want to learn how nvme driver works in Linux,

So I look into nvme driver source code <a href="https://elixir.bootlin.com/linux/v4.10.6/source/drivers/nvme/host" rel="nofollow noreferrer">here</a>

what confuses me is that there are two source file containing "module_init()"

core.c

<pre><code>module_init(nvme_core_init);
</code></pre>

and
pci.c

<pre><code>module_init(nvme_init);
</code></pre>

I know the module_init() function is the entry of the driver

but how come there are two entry in nvme driver ?

difference between core.c and pci.c in Linux nvme driver

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我想知道nvme驱动程序是如何在Linux中工作的，因此，我查看nvme驱动程序源代码。令我困惑的是，有两个源文件包含"module_init()"。core.cmodule_init(nvme_core_init);和太平洋C.module_init(nvme_init);我知道module_init()函数是驱动程...

Linux nvme驱动程序中core.c和pci.c的区别-腾讯云开发者社区-腾讯云

问Linux nvme驱动程序中core.c和pci.c的区别
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Linux nvme驱动程序中core.c和pci.c的区别EN