linux-kernel - Re: per-thread rusage

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

Date:	Wed, 4 Apr 2007 19:48:29 +0200
From:	Eric Dumazet <dada1@...mosbay.com>
To:	William Lee Irwin III <wli@...omorphy.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: per-thread rusage

On Wed, 4 Apr 2007 10:29:31 -0700
William Lee Irwin III <wli@...omorphy.com> wrote:

> It is not now possible for a thread to retrieve its own rusage in
> isolation. Its rusage is nowhere exposed without being intermixed with
> that of its sibling threads. This patch adds support for an
> RUSAGE_THREAD who argument that returns rusage for only the desired
> thread.
> 

Please check mm, because we now return ru_inblock and ru_oublock as well.

r->ru_inblock = task_io_get_inblock(p);
r->ru_oublock = task_io_get_oublock(p);

-
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/