Prev: x86: enlightenment for ticket spin locks - Xen implementation
Next: x86: irq vector assignment
From: Minchan Kim on 30 Jun 2010 10:40
On Wed, Jun 30, 2010 at 06:32:44PM +0900, KOSAKI Motohiro wrote:
>
> Current "child->mm == p->mm" mean prevent to select vfork() task.
> But we don't have any reason to don't consider vfork().

I guess "child->mm == p->mm" is for losing the minimal amount of work done
as comment say. But frankly speaking, I don't understand it, either.
Maybe "One shot, two kill" problem?

Andrea. Could you explain it?

--
Kind regards,
Minchan Kim
--
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: x86: enlightenment for ticket spin locks - Xen implementation
Next: x86: irq vector assignment