linux-kernel - Question about the io_context of I/O scheduler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <458c110a.07a24551.4274.ffff8727@mx.google.com>
Date:	Sat, 23 Dec 2006 01:08:21 +0800
From:	"Roy Lee" <roylee17@...il.com>
To:	<linux-kernel@...r.kernel.org>
Cc:	<roylee17@...il.com>
Subject: Question about the io_context of I/O scheduler

Hi,

I'm currently tracing the I/O path of the kernel (2.6.19 release)

for the I/O scheduler, as far I as know, io_context is currently based on
per-process basis.
so, when an user process issued an I/O, the request generated in the kernel 
will be associated to the io_context of the "current" process, right?

but, isn't there some request generated in the kernel code which is not
relevant to the I/O pattern of the "current" user process?
for example, when the request generated to handle the page fault
or the kernel is paging out other process' pages due to memory pressure.

is this an issue or did I miss something?

thanks in advance for clearifying this.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/