Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 15 Mar 2002 23:27:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 15 Mar 2002 23:27:33 -0500 Received: from h24-83-222-158.vc.shawcable.net ([24.83.222.158]:51590 "EHLO me.bcgreen.com") by vger.kernel.org with ESMTP id ; Fri, 15 Mar 2002 23:27:28 -0500 Message-ID: <3C92C8F0.6070201@bcgreen.com> Date: Fri, 15 Mar 2002 20:24:16 -0800 From: Stephen Samuel Organization: Just Another Radical User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8+) Gecko/20020227 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andreas Ferber CC: Robert Love , torvalds@transmeta.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] syscall interface for cpu affinity In-Reply-To: <1015784104.1261.8.camel@phantasy> <20020311013853.A1545@devcon.net> <3C92704C.1070909@bcgreen.com> <20020316014326.B31470@devcon.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Almost... Same effect (mostly)... It does, however, leaves us arguing the linguistic semantics of which name 'who' should have. It seems to me that the most natural would be with 'who' being the 'name' of the target, and 'which' specifying which name space 'who' is operating in. UGH: messing with these names via pronouns is too confusing: ----------- How about this: int sched_set_affinity(int who, int which, unsigned int len, unsigned long *new_mask_ptr); 'who' being a {process, process-group or user } ID , and with 'which' being one of {PRIO_PROCESS, PRIO_PGRP, PRIO_USER}, respectively -- specifying which namespace 'who' operates in. I think that that is what you were trying to say, right? Andreas Ferber wrote: > On Fri, Mar 15, 2002 at 02:06:04PM -0800, Stephen Samuel wrote: > >> > >> > int sched_set_affinity(int which, int who, unsigned int len, >> > unsigned long *new_mask_ptr); >> > >> > with who one of {PRIO_PROCESS,PRIO_PGRP,PRIO_USER} and which according >> > to the value of who. >> > > Uh, who/which should be just the other way round in the description > (but not in the prototype). Sorry. > > >>I sould suggest that the order be >> >>int sched_set_affinity(int who, int which, unsigned int len, >> unsigned long *new_mask_ptr); >> >>This would have the {p,pg}id be the first thing that a programmer >>would see (likely more important than the 'which'.). -- Stephen Samuel +1(604)876-0426 samuel@bcgreen.com http://www.bcgreen.com/~samuel/ Powerful committed communication, reaching through fear, uncertainty and doubt to touch the jewel within each person and bring it to life. - 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/