Prev: perf, trace: Use per-tracepoint-per-cpu hlist to track events
Next: perf: Drop the skip argument from perf_arch_fetch_regs_caller
From: David Howells on 21 May 2010 06:10
Oleg Nesterov <oleg(a)redhat.com> wrote:

> According to grep, get_nr_threads() becomes the only user of sig->count.

Are these two patches going upstream in this window?

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Oleg Nesterov on 21 May 2010 12:00
On 05/21, David Howells wrote:
>
> Oleg Nesterov <oleg(a)redhat.com> wrote:
>
> > According to grep, get_nr_threads() becomes the only user of sig->count.
>
> Are these two patches going upstream in this window?

We should ask Andrew.

But personally I'd like to see them in 2.6.35. These changes allows
us to do more cleanups/improvements.

As for sizeof(int) added to signal_struct. I still hope we can kill
this "int nr_threads" later. Even if not, with these changes we can
move, say, ->group_leader from task_struct to signal_struct and kill
signal->leader_pid.

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Andrew Morton on 21 May 2010 12:40
On Fri, 21 May 2010 11:08:16 +0100 David Howells <dhowells(a)redhat.com> wrote:

> Oleg Nesterov <oleg(a)redhat.com> wrote:
>
> > According to grep, get_nr_threads() becomes the only user of sig->count.
>
> Are these two patches going upstream in this window?
>

Sure, unless there's a reason not to do this?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: David Howells on 24 May 2010 10:30
Andrew Morton <akpm(a)linux-foundation.org> wrote:

> Sure, unless there's a reason not to do this?

Not that I know of. I was just checking (I'd like to get them out of my patch
stack one way or another).

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: perf, trace: Use per-tracepoint-per-cpu hlist to track events
Next: perf: Drop the skip argument from perf_arch_fetch_regs_caller