[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110516160810.GB25898@one.firstfloor.org>
Date: Mon, 16 May 2011 18:08:10 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Andy Lutomirski <luto@....EDU>
Cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
linux-kernel@...r.kernel.org, libc-alpha@...rceware.org,
Andi Kleen <ak@...ux.intel.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 4/5] Add a sysconf syscall
> You could also add a vsyscall function and have that function pull the
> values from vvar data. It would be very fast (i.e. almost as fast as
> mmaping some data) and it would be more portable.
vvar is a global. The variable data in sysconf is per thread
(and not even per mm)
Even if you ignore the semantic problem of thread versus mm, you would
need a new writable page per process and update it any time
the rlimits and other information is updated.
On the other hand my solution is dead simple and already solves
the problem.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists