Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c

Paul Jackson <[email protected]> writes:

>> Agreed.  However the direction I am gradually moving fs/proc/base.c
>> is the opposite.
>
> Oh - ok fine.
>
> I had seen something from Andrew a couple of days ago
> that led me to a different understanding in this particular
> case.

As we increase the number of namespaces that we allow multiple instances
of in linux.  More of the files that are in /proc need to become
per process, like /proc/mounts did.

I mentioned that to Andrew and I think the message got a little
garbled.

Eric
-
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:
- [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
  - From: Paul Jackson <[email protected]>
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
  - From: Christoph Hellwig <[email protected]>
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
  - From: Paul Jackson <[email protected]>
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
  - From: [email protected] (Eric W. Biederman)
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
  - From: Paul Jackson <[email protected]>

Prev by Date: Re: Question: how to map SCSI data DMA address to virtual address?
Next by Date: Re: Another compile problem with 2.6.15.5 on AMD64
Previous by thread: Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
Next by thread: [PATCH] Define BITS_PER_BYTE to fix compilation error in 2.6.15.5
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]