From owner-freebsd-arch@FreeBSD.ORG Wed Sep 3 10:57:48 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 751EB30B for ; Wed, 3 Sep 2014 10:57:48 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3EFCC1436 for ; Wed, 3 Sep 2014 10:57:48 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id h3so5103558igd.1 for ; Wed, 03 Sep 2014 03:57:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4+5gfG+NkzbHbnCB6lZ+5+Kd9izb+eMwp1qdwbeEYQg=; b=k/6G8SAwLoAsdGseJVXUYRX9pvapwmRyltQ1hgTPeylzuzIZ2z2WZ3fBqWtLWOKyVO Cp3ZvScjKbe8Qo+kptXB24jkRLqt2nyusiHk/5OvQgVu64cjMFBv7hXQLM4tDPi9XgvC IgGkVY66TKK156Zcl13McydiygKJ7U/7V0+LcMN2WaBOFVrDmDYyi3BsmZUqqr2CTCtU KixjSYJ3HMWH8w6jPb7eMFAhpupbKH3xDMLDhcWyevlfEJJAQXhp1wWdATlIpIT12lGZ 1rOzKUu2rNKKxskLnC2IpiTmJTjlbmotTmVV0IkuOHEdGjEypnFsZVl/3/oTarwxSvUV GH4Q== MIME-Version: 1.0 X-Received: by 10.50.26.66 with SMTP id j2mr35958930igg.45.1409741867563; Wed, 03 Sep 2014 03:57:47 -0700 (PDT) Received: by 10.107.129.25 with HTTP; Wed, 3 Sep 2014 03:57:47 -0700 (PDT) In-Reply-To: <20140902193211.GA29155@nbu> References: <20140529102054.GX50679@FreeBSD.org> <20140729232404.GF43962@funkthat.com> <20140831165022.GE7693@FreeBSD.org> <540382E2.3040004@freebsd.org> <2770.1409522711@critter.freebsd.dk> <5403B13C.60008@freebsd.org> <4204.1409549879@critter.freebsd.dk> <5404D1B8.9010006@mu.org> <40210.1409607245@critter.freebsd.dk> <20140902193211.GA29155@nbu> Date: Wed, 3 Sep 2014 12:57:47 +0200 Message-ID: Subject: Re: script(2) [was: [CFT/review] new sendfile(2)] From: Johan Bucht To: Walt Ford Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Poul-Henning Kamp , Alfred Perlstein , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 10:57:48 -0000 Example of Lua packet filtering: http://wingolog.org/archives/2014/09/02/high-performance-packet-filtering-with-pflua On Tue, Sep 2, 2014 at 9:32 PM, Walt Ford via freebsd-arch < freebsd-arch@freebsd.org> wrote: > On Mon, Sep 01, 2014 at 09:34:05PM +0000, Poul-Henning Kamp wrote: > > In message <5404D1B8.9010006@mu.org>, Alfred Perlstein writes: > >>> In message <5403B13C.60008@freebsd.org>, Alfred Perlstein writes: > >>> > >>>> Lua at the syscall level makes sense. :) > >>> I doubt it. > >>> > >>> We're looking at high performance stuff and we don't want a silly > >>> parser and string processing involved. > >>> > >>Would it really matter? Lua is bytecode, [...] > > > > I though you wanted the interpreter in the kernel. > > > > If it's only the executor, then ... maybe... > > > > We'd need to do a serious audit of the lua bytecode first... > > I've been sort of working on a Lua-based FreeBSD for years in my spare > time just because I love both so much. I could be wrong, but I think > making use of Lua in-kernel would require modifying the interpreter to > include the kernel's idea of locks, mutexes, memory barriers, and threads. > In Lua, threads and their safety must be written by end-users last I knew, > but I don't follow Lua development closely. > > At least in my latest work, trying to replace init_main.c and mi_startup() > with a Lua script, all of that is necessary. Really, I'd even need the > interpreter to be aware of the FreeBSD scheduler for a Lua-based mi_startup > to be workable. > > I've got a lot of Lua bits and pieces in userland utilities, libraries, > and now init_main.c is in boot/ but none of it works yet. I have visions > of a FreeBSD that unboot backwards to reload subsystems, but I'm not > close. > > -- > Walt > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >