mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@tv-sign.ru>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] worker_thread: don't play with SIGCHLD
Date: Fri, 13 Apr 2007 17:40:46 +0400	[thread overview]
Message-ID: <20070413134046.GA180@tv-sign.ru> (raw)
In-Reply-To: <m1irc0pfyq.fsf@ebiederm.dsl.xmission.com>

On 04/13, Eric W. Biederman wrote:
>
> Oleg Nesterov <oleg@tv-sign.ru> writes:
> 
> > depends on Eric's
> >
> > 	kthread-dont-depend-on-work-queues-take-2.patch
> >
> > worker_thread() inherits ignored SIGCHLD from its parent, kthreadd.
> > We can remove unneeded do_sigaction().
> 
> Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
> 
> Looks good.
> 
> We could delete all of:
> 
> > 	set_user_nice(current, -5);
> > 
> > 	/* Block and flush all signals */
> > 	sigfillset(&blocked);
> > 	sigprocmask(SIG_BLOCK, &blocked, NULL);
> > 	flush_signals(current);

this one is already deleted in -mm...

> > 	/*
> > 	 * We inherited MPOL_INTERLEAVE from the booting kernel.
> > 	 * Set MPOL_DEFAULT to insure node local allocations.
> > 	 */
> > 	numa_default_policy();

Yes, I forgot about this!

> If we wanted to, as that all comes by default from kthreadd.

Thanks, will send an update.

Oleg.


  reply	other threads:[~2007-04-13 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13  7:29 Oleg Nesterov
2007-04-13 13:21 ` Eric W. Biederman
2007-04-13 13:40   ` Oleg Nesterov [this message]
2007-04-13 13:54     ` [PATCH] worker_thread: don't play with SIGCHLD and numa policy Oleg Nesterov

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=20070413134046.GA180@tv-sign.ru \
    --to=oleg@tv-sign.ru \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®