On Sat, Mar 20, 2010 at 12:20:58PM -0700, Linus Torvalds wrote:
quoted text
> 
> 
> On Fri, 5 Mar 2010, Jiri Slaby wrote:
> > 
> > please pull the writable limits tree below.
> 
> Ok, sorry for the long delay - I spent 5 days at two separate intel events 
> over the last two weeks, which ended up sucking up a lot of my spare time 
> that I normally use to try to judge the merge window stuff. As a result, I 
> pulled mainly code that wasn't new (ie existing models), or that was 
> "obviously independent" (liek the new ceph filesystem) and didn't have any 
> contentious issues.
> 
> As a result, I ended up looking at the writable limits only today.
> 
> And I'm not entirely happy. For example, I absolutely _detest_ seeing new 
> compat code for a feature that was just added. My immediate reaction is 
> "WTF? What kind of moron doesn't make things 64-bit safe to begin with?". 
> It's really annoying.
> 
> Why doesn't the new set/getprlimit things just take a pointer to a 
> well-defined pair of 64-bit values? Why is there any compat cruft at all 
> there? That is beyond insane. Just make the user level interface work 
> right in the first place, instead of adding crazy compat crap. This is 
> _not_ a legacy interface.
> 
I won't speak to this yet, its been awhile since I looked at it, but I don't
recall there being any compat code in place (although it went through several
revisions, so I may be thinking of the wrong version).

quoted text
> I'd also like to hear more about actual uses. Does _any_ other Unix-like 
> system actually implement this writable limits thing? Who is asking for 
> it? 
> 
The main request that I've gotten in regards to this feature request is for
admins who want to make limits adjustments to processes without the need to
restart them.  The specific example I've been given is the desire to increase
the number of open files a database process can hold without needing to restart
the database.

Neil

quoted text
> 			Linus
> 
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/