All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Roland McGrath <roland@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: do_wait() changes && 2.6.32 -mm merge plans
Date: Thu, 17 Sep 2009 22:32:48 +0200	[thread overview]
Message-ID: <20090917203248.GB29346@redhat.com> (raw)
In-Reply-To: <20090915161535.db0a6904.akpm@linux-foundation.org>

On 09/15, Andrew Morton wrote:
>
> ptrace-__ptrace_detach-do-__wake_up_parent-if-we-reap-the-tracee.patch
> do_wait-wakeup-optimization-shift-security_task_wait-from-eligible_child-to-wait_consider_task.patch
> #do_wait-wakeup-optimization-change-__wake_up_parent-to-use-filtered-wakeup.patch: busted (KAMEZAWA)
> do_wait-wakeup-optimization-change-__wake_up_parent-to-use-filtered-wakeup.patch

Hopefully the problem with this one is fixed, thanks again to Kamezawa.

> do_wait-wakeup-optimization-change-__wake_up_parent-to-use-filtered-wakeup-selinux_bprm_committed_creds-use-__wake_up_parent.patch
> do_wait-wakeup-optimization-child_wait_callback-check-__wnothread-case.patch
> do_wait-wakeup-optimization-fix-child_wait_callback-eligible_child-usage.patch
> do_wait-wakeup-optimization-simplify-task_pid_type.patch
> #do_wait-optimization-do-not-place-sub-threads-on-task_struct-children-list.patch: risky?
> do_wait-optimization-do-not-place-sub-threads-on-task_struct-children-list.patch

Yes, risky... God knows who can do list_for_each(->children) and expect to
find the sub-threads. But this is obviously good optimization/simplification.

It is just ugly to place sub-threads on ->children list, this buys nothing
but slown downs do_wait(). (this was needed, afaics, to handle ptraced but
not re-parented threads a long ago).

> wait_consider_task-kill-parent-argument.patch
> do_wait-fix-sys_waitid-specific-behaviour.patch
> wait_noreap_copyout-check-for-wo_info-=-null.patch
>
>   ptrace.  Mostly-merge.

Only the first patch is "ptrace" ;)

Oleg.


WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Roland McGrath <roland@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: do_wait() changes && 2.6.32 -mm merge plans
Date: Thu, 17 Sep 2009 22:32:48 +0200	[thread overview]
Message-ID: <20090917203248.GB29346@redhat.com> (raw)
In-Reply-To: <20090915161535.db0a6904.akpm@linux-foundation.org>

On 09/15, Andrew Morton wrote:
>
> ptrace-__ptrace_detach-do-__wake_up_parent-if-we-reap-the-tracee.patch
> do_wait-wakeup-optimization-shift-security_task_wait-from-eligible_child-to-wait_consider_task.patch
> #do_wait-wakeup-optimization-change-__wake_up_parent-to-use-filtered-wakeup.patch: busted (KAMEZAWA)
> do_wait-wakeup-optimization-change-__wake_up_parent-to-use-filtered-wakeup.patch

Hopefully the problem with this one is fixed, thanks again to Kamezawa.

> do_wait-wakeup-optimization-change-__wake_up_parent-to-use-filtered-wakeup-selinux_bprm_committed_creds-use-__wake_up_parent.patch
> do_wait-wakeup-optimization-child_wait_callback-check-__wnothread-case.patch
> do_wait-wakeup-optimization-fix-child_wait_callback-eligible_child-usage.patch
> do_wait-wakeup-optimization-simplify-task_pid_type.patch
> #do_wait-optimization-do-not-place-sub-threads-on-task_struct-children-list.patch: risky?
> do_wait-optimization-do-not-place-sub-threads-on-task_struct-children-list.patch

Yes, risky... God knows who can do list_for_each(->children) and expect to
find the sub-threads. But this is obviously good optimization/simplification.

It is just ugly to place sub-threads on ->children list, this buys nothing
but slown downs do_wait(). (this was needed, afaics, to handle ptraced but
not re-parented threads a long ago).

> wait_consider_task-kill-parent-argument.patch
> do_wait-fix-sys_waitid-specific-behaviour.patch
> wait_noreap_copyout-check-for-wo_info-=-null.patch
>
>   ptrace.  Mostly-merge.

Only the first patch is "ptrace" ;)

Oleg.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2009-09-17 20:37 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 23:15 2.6.32 -mm merge plans Andrew Morton
2009-09-15 23:15 ` Andrew Morton
2009-09-16  0:03 ` Paul Mundt
2009-09-16  0:03   ` Paul Mundt
2009-09-16  0:18   ` Andrew Morton
2009-09-16  0:18     ` Andrew Morton
2009-09-16  3:51     ` Mike Frysinger
2009-09-16  3:51       ` Mike Frysinger
2009-09-16  4:15       ` Andrew Morton
2009-09-16  4:15         ` Andrew Morton
2009-09-16  4:17         ` Mike Frysinger
2009-09-16  4:17           ` Mike Frysinger
2009-09-16  7:21       ` Artem Bityutskiy
2009-09-16  7:21         ` Artem Bityutskiy
2009-09-16  7:09   ` Artem Bityutskiy
2009-09-16  7:36     ` Artem Bityutskiy
2009-09-16  3:46 ` Dmitry Torokhov
2009-09-16  3:46   ` Dmitry Torokhov
2009-09-16  4:14   ` Andrew Morton
2009-09-16  4:14     ` Andrew Morton
2009-09-16  8:33     ` David Härdeman
2009-09-16  8:33       ` David Härdeman
2009-09-16 15:00     ` Bjorn Helgaas
2009-09-16 15:00       ` Bjorn Helgaas
2009-09-16 20:00       ` Andrew Morton
2009-09-16 20:00         ` Andrew Morton
2009-09-16  7:37 ` memcg merge for 2.6.32 (was Re: 2.6.32 -mm merge plans) Balbir Singh
2009-09-16  7:37   ` Balbir Singh
2009-09-16  7:51   ` Daisuke Nishimura
2009-09-16  7:51     ` Daisuke Nishimura
2009-09-16  7:58   ` KAMEZAWA Hiroyuki
2009-09-16  7:58     ` KAMEZAWA Hiroyuki
2009-09-16  8:45 ` stack limits [was Re: 2.6.32 -mm merge plans] Pavel Machek
2009-09-16  8:45   ` Pavel Machek
2009-09-16  9:42 ` hwpoison fixes was Re: 2.6.32 -mm merge plans Andi Kleen
2009-09-16  9:42   ` Andi Kleen
2009-09-17 20:15 ` cgrooups && " Oleg Nesterov
2009-09-17 20:15   ` Oleg Nesterov
2009-09-17 20:38   ` Andrew Morton
2009-09-17 20:38     ` Andrew Morton
2009-09-17 21:08     ` Oleg Nesterov
2009-09-17 21:08       ` Oleg Nesterov
2009-09-17 20:32 ` Oleg Nesterov [this message]
2009-09-17 20:32   ` do_wait() changes " Oleg Nesterov
2009-09-17 20:46 ` tracehooks " Oleg Nesterov
2009-09-17 20:46   ` Oleg Nesterov
2009-09-17 21:56   ` Roland McGrath
2009-09-17 21:56     ` Roland McGrath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090917203248.GB29346@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=roland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.