From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <437996A2.1090808@domain.hid> Date: Tue, 15 Nov 2005 09:04:50 +0100 From: Philippe Gerum MIME-Version: 1.0 Subject: Re: [Xenomai-help] xn_pipe_create [minor] References: <4378CBA6.6000708@domain.hid> <200511141933.26292.dmitry.adamushko@domain.hid> In-Reply-To: <200511141933.26292.dmitry.adamushko@domain.hid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dmitry Adamushko Cc: xenomai@xenomai.org Dmitry Adamushko wrote: > On Monday 14 November 2005 18:38, Philippe Gerum wrote: > >>xenomai@xenomai.org > > >>>If you want to have some fun (and you have some time and desire for >>>that) then go ahead :) Otherwise, no problem, I'll do that. >>> >> >>Please make sure to implement this at the nucleus level, and if using a >>bitmap to locate free/busy slots, it should be large enough to handle >>FDSETSIZE channels, not BITS_PER_LONG. > > > We have xnpipe_states[XNPIPE_DEVS] array of pipe objects. Choosing a minor > value is about choosing a free slot (minor == id of that slot) so there are > XNPIPE_DEVS possible values. The bitmap must contain at least XNPIPE_DEVS > bits. I don't understand what FDSETSIZE has to do here (if you mean the one > that is used to configure select() behaviour). The point is about not being limited to the number of bits in a long, because I know of configurations with more than 32 active channels. IOW, #define XNPIPE_DEVS FDSETSIZE should be possible. > > >>-- >> >>Philippe. > > > --- > > Dmitry > -- Philippe.