Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-21 Thread Taylor R Campbell
Date: Sat, 19 Oct 2013 09:47:14 +0200 From: Marc Balmer And now to give you a practical example what I personally do with lua(4) right now: In the past I wrote several tty line disciplines to decode various serial formats. Now I have a need for that again. Doing this in C is

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-19 Thread Yann Sionneau
Le 19/10/13 00:47, Marc Balmer a écrit : Am 19.10.13 00:14, schrieb Aleksej Saushev: [...] I'm of opinion that this device driver can and should stay outside the tree until its utility can be demonstrated without this much strain. At last this is one of the reasons why we support kernel module

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-19 Thread Alan Barrett
On Sat, 19 Oct 2013, Marc Balmer wrote: And now to give you a practical example what I personally do with lua(4) right now: In the past I wrote several tty line disciplines to decode various serial formats. Now I have a need for that again. Doing this in C is of course possible, but I want som

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-19 Thread Matt Thomas
On Oct 19, 2013, at 12:26 AM, Marc Balmer wrote: > Am 19.10.13 09:03, schrieb Alan Barrett: >> On Sat, 19 Oct 2013, Marc Balmer wrote: >>> The inclusion and use of Lua in base, for use in userland and the >>> kernel, [...] has, last but not least, core's blessing. >> >> Would you please either

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-19 Thread Marc Balmer
Am 19.10.13 09:12, schrieb Alan Barrett: > On Fri, 18 Oct 2013, Lourival Vieira Neto wrote: >>> I have to point out that "interesting work" is commonly used as a >>> sort of euphemism to refer to highly experimental work with unclear >>> future. >> >> Yes. But I'm talking about "interesting *user*

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-19 Thread Marc Balmer
Am 19.10.13 09:03, schrieb Alan Barrett: > On Sat, 19 Oct 2013, Marc Balmer wrote: >> The inclusion and use of Lua in base, for use in userland and the >> kernel, [...] has, last but not least, core's blessing. > > Would you please either present some evidence for that claim, or stop > making the

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-19 Thread Alan Barrett
On Fri, 18 Oct 2013, Lourival Vieira Neto wrote: I have to point out that "interesting work" is commonly used as a sort of euphemism to refer to highly experimental work with unclear future. Yes. But I'm talking about "interesting *user* work". I'm not claiming that they should be in the kern

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-19 Thread Alan Barrett
On Sat, 19 Oct 2013, Marc Balmer wrote: The inclusion and use of Lua in base, for use in userland and the kernel, [...] has, last but not least, core's blessing. Would you please either present some evidence for that claim, or stop making the claim. To the best of my knowledge, userland Lua

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Taylor R Campbell
Date: Fri, 18 Oct 2013 18:12:29 -0300 From: Lourival Vieira Neto On Fri, Oct 18, 2013 at 9:08 AM, Taylor R Campbell wrote: > [*] You could do this in a branch, you could do this in a private Git > repository, or you could even just do this in a local CVS checkout > (since kern

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Lourival Vieira Neto
>>>Lua is a tool, not an end in itself. I think that you are formulating >>>a chicken-and-egg problem: we need the basic support for then having >>>applications, and we need applications for then having basic support. >>> >>> This is not a chicken-and-egg problem. You can make an exper

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Lourival Vieira Neto
Lua is a tool, not an end in itself. I think that you are formulating a chicken-and-egg problem: we need the basic support for then having applications, and we need applications for then having basic support. >>> >>> The problem with your approach is that such "chicken-and-egg" probl

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Marc Balmer
Am 19.10.13 00:14, schrieb Aleksej Saushev: [...] > I'm of opinion that this device driver can and should stay outside the tree > until its utility can be demonstrated without this much strain. > At last this is one of the reasons why we support kernel modules. The inclusion and use of Lua in ba

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Aleksej Saushev
Hello, Lourival Vieira Neto writes: > On Fri, Oct 18, 2013 at 9:08 AM, Taylor R Campbell > wrote: >>Date: Thu, 17 Oct 2013 19:16:16 -0300 >>From: Lourival Vieira Neto >> >>Lua is a tool, not an end in itself. I think that you are formulating >>a chicken-and-egg problem: we n

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Aleksej Saushev
Hello, Lourival Vieira Neto writes: > On Fri, Oct 18, 2013 at 1:31 PM, Aleksej Saushev wrote: >> (...) >>> Lua is a tool, not an end in itself. I think that you are formulating >>> a chicken-and-egg problem: we need the basic support for then having >>> applications, and we need applications

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Lourival Vieira Neto
Hi, On Fri, Oct 18, 2013 at 1:31 PM, Aleksej Saushev wrote: > (...) >> Lua is a tool, not an end in itself. I think that you are formulating >> a chicken-and-egg problem: we need the basic support for then having >> applications, and we need applications for then having basic support. > > The pro

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Lourival Vieira Neto
On Fri, Oct 18, 2013 at 9:08 AM, Taylor R Campbell wrote: >Date: Thu, 17 Oct 2013 19:16:16 -0300 >From: Lourival Vieira Neto > >Lua is a tool, not an end in itself. I think that you are formulating >a chicken-and-egg problem: we need the basic support for then having >applicat

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Lourival Vieira Neto
Hi, On Fri, Oct 18, 2013 at 11:09 AM, Matt W. Benjamin wrote: > Hi, > > The linked research was performed on Linux, which has NFsv4.1 and pNFS client > implementations. Evidently, you can do this kind of thing with an out-of-tree > Lua kernel extension. > > Matt Evidently. I'm not arguing that

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread D'Arcy J.M. Cain
On Fri, 18 Oct 2013 20:31:05 +0400 Aleksej Saushev wrote: > I doubt very much that we want such unreliable development practices > like "agile" ones in the kernel, and experimentation work can be done > easier and better in a branch or a personal repository. I think I agree with your sentiment bu

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Aleksej Saushev
Hello, Lourival Vieira Neto writes: > On Thu, Oct 17, 2013 at 1:26 PM, Jeff Rizzo wrote: >> On 10/14/13 1:46 PM, Marc Balmer wrote: >>> >>> There is real word, real working code. In userland and in kernel space. >>> There are developers waiting for the kernel parts to be committet, so >>>

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Matt W. Benjamin
Hi, The linked research was performed on Linux, which has NFsv4.1 and pNFS client implementations. Evidently, you can do this kind of thing with an out-of-tree Lua kernel extension. Matt - "Taylor R Campbell" wrote: > >[1] https://github.com/dergraf/PacketScript > >[2] http://ww

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-18 Thread Taylor R Campbell
Date: Thu, 17 Oct 2013 19:16:16 -0300 From: Lourival Vieira Neto Lua is a tool, not an end in itself. I think that you are formulating a chicken-and-egg problem: we need the basic support for then having applications, and we need applications for then having basic support. This is

Re: Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-17 Thread Lourival Vieira Neto
Hi Jeff, On Thu, Oct 17, 2013 at 1:26 PM, Jeff Rizzo wrote: > On 10/14/13 1:46 PM, Marc Balmer wrote: >> >> >>> It is entirely plausible to me that we could benefit from using Lua in >>> base, or sysinst, or maybe even in the kernel. But that argument must >>> be made by showing evidence of real

Why do we need lua in-tree again? Yet another call for actual evidence, please. (was Re: Moving Lua source codes)

2013-10-17 Thread Jeff Rizzo
On 10/14/13 1:46 PM, Marc Balmer wrote: It is entirely plausible to me that we could benefit from using Lua in base, or sysinst, or maybe even in the kernel. But that argument must be made by showing evidence of real, working code that has compelling benefits, together with confidence in its r