Re: cpuset trouble after hibernate

On 9/15/07, Andrew Morton <[email protected]> wrote:
>
> Yeah.  Bug, surely.  But I guess it's always been there.
>
> What are the implications of this for cpusets-via-containers?
>

I don't think it should be any different from the previous version - I
tried to avoid touching those bits of cpusets where possible.

Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • cpuset trouble after hibernate
    • From: Nicolas Capit <[email protected]>
  • Re: cpuset trouble after hibernate
    • From: Simon Derr <[email protected]>
  • Re: cpuset trouble after hibernate
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: Wasting our Freedom
• Next by Date: Re: [PATCH] task containersv11 enable containers by default in some configs
• Previous by thread: Re: cpuset trouble after hibernate
• Next by thread: Re: cpuset trouble after hibernate
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]