linux-kernel - Re: How does CFQ handle the fairness of process write

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTimQhy9X_dEx6D_trNRcxtz3BGjjRqzFEf1iCDPR@mail.gmail.com>
Date:	Mon, 24 Jan 2011 17:32:22 +0900
From:	Nauman Rafique <nauman@...gle.com>
To:	Yuehai Xu <yuehaixu@...il.com>
Cc:	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
	yhxu@...ne.edu
Subject: Re: How does CFQ handle the fairness of process write

Yuehai,
You have got it right. CFQ is not able to attribute writes to the
threads which actually submit the writes, unless the writes are done
in a synchronous mode (the ones coming through fsync, etc) or in
O_DIRECT mode where the writes are submitted in the context of the
thread itself.

Some attempts have been made in the past to help with this problem. In
the patch series at http://lkml.org/lkml/2010/7/8/478, Munehiro Ikeda
added support for tracking the cgroup (not thread) of the writer
threads, but the patches were not merged. You can read the discussion
there to find out the objections to getting the patches merged (which
I don't necessarily agree with).Tracking the actual thread (instead of
cgroup) of the writer would be the next logical step after those
patches are merged.

In summary, it is a known problem, and hopefully would get fixed one day.

On Sun, Jan 23, 2011 at 9:49 AM, Yuehai Xu <yuehaixu@...il.com> wrote:
> Hi all,
>
> Suppose there are two processes writing lots of data to disk, these
> data are written to cache at first, and then, kernel threads might
> flush them to disk later. However, from the point of block device, the
> kernel thread is just another process that issues write requests. So,
> how does CFQ handle the fairness between the two processes? It is
> impossible for CFQ to keep the fairness of the two queues for each
> process since many write requests are dispatched by kernel thread,
> which has another queue in CFQ. And both the requests from two
> processes are mixed together in this kernel thread queue.
>
> Is this description correct? In that case, how does CFQ keep the
> fairness for two processes since CFQ seems unable to know the exact
> process the request belongs to.
>
> I appreciate your help.
>
> Thanks,
> Yuehai
> --
> 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/
>
--
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/