对于较新的 linux 内核，刷新进程名称中的数字有什么意义？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/4621948/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
What is the significance of the numbers in the name of the flush processes for newer linux kernels?
提问by HBlend
I am running kernel 2.6.33.7.
我正在运行内核 2.6.33.7。
Previously, I was running v2.6.18.x. On 2.6.18, the flush processes were named pdflush.
以前，我运行的是 v2.6.18.x。在 2.6.18 上，刷新进程被命名为 pdflush。
After upgrading to 2.6.33.7, the flush processes have a format of "flush-:". For example, currently I see flush process "flush-8:32" popping up in top.
升级到 2.6.33.7 后，刷新进程的格式为“flush-:”。例如，目前我看到刷新进程“flush-8:32”弹出顶部。
In doing a google search to try to determine an answer to this question, I saw examples of "flush-8:38", "flush-8:64" and "flush-253:0" just to name a few.
在进行谷歌搜索以确定这个问题的答案时，我看到了“flush-8:38”、“flush-8:64”和“flush-253:0”的例子，仅举几例。
I understand what the flush process itself does, my question is what is the significance of the numbers on the end of the process name? What do they represent?
我了解刷新进程本身的作用，我的问题是进程名称末尾的数字有什么意义？它们代表什么？
Thanks
谢谢
采纳答案by ephemient
Device numbers used to identify block devices. A kernel thread may be spawned to handle a particular device.
用于标识块设备的设备号。可以产生内核线程来处理特定设备。
(On one of my systems, block devices are currently numbered as shown below. They may change from boot to boot or hotplug to hotplug.)
（在我的一个系统上，块设备当前的编号如下所示。它们可能会从引导更改为引导或热插拔到热插拔。）
$ grep ^ /sys/class/block/*/dev /sys/class/block/dm-0/dev:254:0 /sys/class/block/dm-1/dev:254:1 /sys/class/block/dm-2/dev:254:2 /sys/class/block/dm-3/dev:254:3 /sys/class/block/dm-4/dev:254:4 /sys/class/block/dm-5/dev:254:5 /sys/class/block/dm-6/dev:254:6 /sys/class/block/dm-7/dev:254:7 /sys/class/block/dm-8/dev:254:8 /sys/class/block/dm-9/dev:254:9 /sys/class/block/loop0/dev:7:0 /sys/class/block/loop1/dev:7:1 /sys/class/block/loop2/dev:7:2 /sys/class/block/loop3/dev:7:3 /sys/class/block/loop4/dev:7:4 /sys/class/block/loop5/dev:7:5 /sys/class/block/loop6/dev:7:6 /sys/class/block/loop7/dev:7:7 /sys/class/block/md0/dev:9:0 /sys/class/block/md1/dev:9:1 /sys/class/block/sda/dev:8:0 /sys/class/block/sda1/dev:8:1 /sys/class/block/sda2/dev:8:2 /sys/class/block/sdb/dev:8:16 /sys/class/block/sdb1/dev:8:17 /sys/class/block/sdb2/dev:8:18 /sys/class/block/sdc/dev:8:32 /sys/class/block/sdc1/dev:8:33 /sys/class/block/sdc2/dev:8:34 /sys/class/block/sdd/dev:8:48 /sys/class/block/sdd1/dev:8:49 /sys/class/block/sdd2/dev:8:50 /sys/class/block/sde/dev:8:64 /sys/class/block/sdf/dev:8:80 /sys/class/block/sdg/dev:8:96 /sys/class/block/sdh/dev:8:112 /sys/class/block/sdi/dev:8:128 /sys/class/block/sr0/dev:11:0 /sys/class/block/sr1/dev:11:1 /sys/class/block/sr2/dev:11:2
回答by mkomitee
You should also be able to figure this out by searching for those numbers in /proc/self/mountinfo, eg:
您还应该能够通过在 /proc/self/mountinfo 中搜索这些数字来弄清楚这一点，例如：
$ grep 8:32 /proc/self/mountinfo
25 22 8:32 / /var rw,relatime - ext4 /dev/mapper/sysvg-var rw,barrier=1,data=ordered
This has the side benefit of working with nfs as well:
这也有使用 nfs 的附带好处：
$ grep 0:73 /proc/self/mountinfo
108 42 0:73 /foo /mnt/foo rw,relatime - nfs host.domain.com:/volume/path rw, ...
Note, the data I included here is fabricated, but the mechanism works just fine.
请注意，我在此处包含的数据是捏造的，但该机制工作正常。
