Re: [patch02/05]: Containers(V2)- Generic Linux kernel changes

Rohit Seth <[email protected]> writes:
>  					 */
> +#ifdef CONFIG_CONTAINERS
> +	struct container_struct *ctn; /* Pointer to container, may be NULL */
> +#endif

I still don't think it's a good idea to add a pointer to struct page for this.
This means any kernel that enables the config would need to carry this significant
overhead, no matter if containers are used to not.

Better would be to store them in some other data structure that is only
allocated on demand or figure out a way to store them in the sometimes
not all used fields in struct page.

BTW your patchkit seems to be also in wrong order in that when 02 is applied
it won't compile.

-Andi
-
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/

---

• Follow-Ups:
  • Re: [patch02/05]: Containers(V2)- Generic Linux kernel changes
    • From: Rohit Seth <[email protected]>

• References:
  • [patch02/05]: Containers(V2)- Generic Linux kernel changes
    • From: Rohit Seth <[email protected]>

• Prev by Date: [PATCH]: cciss - remove unneeded spaces in output for attached volumes (resend)
• Next by Date: Allocated large blocks of memory on 64 bit linux.
• Previous by thread: [patch02/05]: Containers(V2)- Generic Linux kernel changes
• Next by thread: Re: [patch02/05]: Containers(V2)- Generic Linux kernel changes
• 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]