Re: Honest does not pay here ...

if I understand your point, a vendor could ask to the end user to apply a patch
to the new kernels, so that modules infrastructure will be changed, and also non
GPLed modules can create their own run queue.

Yes, it is possible, because we are talking about open source (I mean a more
generic definition instead of free-software, i.e. all the software that comes
with source code). I would add, it's in the rules of the game.
But developers for this patch have to be paid, and
patch could create conflicts, and has to be maintained togheter with the
binary only module (depends on costs).

To say the truth, I do not even expect end users to care if the modules is
running with its own kernel threads in his own run queue, or it is using the
defaul queue.

Anyway I found the runqueue concept, as it has been implemented, an
equilibrate and factual solution to incentivate companies to GPL their code,
and I was surprised that none (except a short allusion from you),
in two threads took the opportunity to talk about a fact and a good point.

Luigi Genoni

On Tue, 7 Jan 2003, Andre Hedrick wrote:

> Date: Tue, 7 Jan 2003 17:10:41 -0800 (PST)
> From: Andre Hedrick <[e-mail]>
> To: [e-mail]
> Cc: Larry McVoy <[e-mail]>, Matthias Andree <[e-mail]>,
>      [e-mail]
> Subject: Re: Honest does not pay here ...
>
>
> Luigi,
>
> You forgot one thing.  None of us can control what the end user does.
> If a vendor tells the enduser to alter the 2.5/2.6 kernel and recompile.
> What are you going to do?
>
> Add a clause where the enduser can not change the source code or apply a
> patch to do it for them?
>
> Funny, you lost your rights to do that w/ GPL, as did I.
>
> *sigh*
>
> Andre Hedrick
> LAD Storage Consulting Group
>
> On Wed, 8 Jan 2003 [e-mail] wrote:
>
> >
> > well, I was forgetting to specify,
> > queues are kernel threads, and that is quite
> > optimum expecially on SMP systems.
> > One big advantage is that conflicts possibilities are
> > (should be) less than minimal.
> >
> > Luigi
> >
> > On Tue, 7 Jan 2003, Larry McVoy wrote:
> >
> > > Date: Tue, 7 Jan 2003 16:30:50 -0800
> > > From: Larry McVoy <[e-mail]>
> > > To: [e-mail]
> > > Cc: Matthias Andree <[e-mail]>, [e-mail],
> > >      [e-mail]
> > > Subject: Re: Honest does not pay here ...
> > >
> > >
> > > > In very semplicistic words:
> > > > In 2.5/2.6 kernels, non GPL modules have a big
> > > > penalty, because they cannot create their own queue, but have to use a default
> > > > one.
> > >
> > > I may be showing my ignorance here (won't be the first time) but this makes
> > > me wonder if Linux could provide a way to do "user level drivers".  I.e.,
> > > drivers which ran in kernel mode but in the context of a process and had
> > > to talk to the real kernel via pipes or whatever.  It's a fair amount of
> > > plumbing but could have the advantage of being a more stable interface
> > > for the drivers.
> > >
> > > If you think about it, drivers are more or less open/close/read/write/ioctl.
> > > They need kernel privileges to do their thing but don't need (and shouldn't
> > > have) access to all the guts of the kernel.
> > >
> > > Can any well traveled driver people see this working or is it nuts?
> > > --
> > > ---
> > > Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm
> > >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [e-mail]
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
>