Andrew Morton wrote:
>> But then again, if it was possible to write 100 lines of userspace code, we
>> wouldn't need this capability at all. I bet if the userspace guys tried a
>> bit harder they'd work out a way of teaching their applications to remember
>> what they did.
On Thu, Nov 10, 2005 at 06:49:56PM -0800, Arun Sharma wrote:
> Why do we need shmctl(IPC_STAT) then? Applications should remember what
> they did :)
atime, dtime, ctime, lpid, and nattch are not "rememberable" this way.
-- wli
-
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] Expose SHM_HUGETLB in shmctl(id, IPC_STAT, ...)
- Re: [PATCH] Expose SHM_HUGETLB in shmctl(id, IPC_STAT, ...)
- Re: [PATCH] Expose SHM_HUGETLB in shmctl(id, IPC_STAT, ...)
- Re: [PATCH] Expose SHM_HUGETLB in shmctl(id, IPC_STAT, ...)
- Re: [PATCH] Expose SHM_HUGETLB in shmctl(id, IPC_STAT, ...)
- Re: [PATCH] Expose SHM_HUGETLB in shmctl(id, IPC_STAT, ...)
- Re: [PATCH] Expose SHM_HUGETLB in shmctl(id, IPC_STAT, ...)
[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]