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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Re: 2.6.19 file content corruption on ext3
• Next by Date: [PATCH] Fix some ARM builds due to HID brokenness
• Previous by thread: [PATCH] Make mkcompile_h use LANG=C and LC_ALL=C for $CC -v
• Next by thread: [PATCH] Fix some ARM builds due to HID brokenness
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]