From owner-freebsd-hackers Sun Jun 18 21: 9:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbgroup.co.nz (gateway.kbgroup.co.nz [203.96.151.81]) by hub.freebsd.org (Postfix) with ESMTP id DC01237BB5D for ; Sun, 18 Jun 2000 21:09:37 -0700 (PDT) (envelope-from dave.preece@kbgroup.co.nz) Received: from kb_exchange.kbgroup.co.nz ([202.202.203.10]) by gateway.kbgroup.co.nz with ESMTP id <115201>; Mon, 19 Jun 2000 16:26:50 +1200 Received: by internet.kbgroup.co.nz with Internet Mail Service (5.5.2650.21) id ; Mon, 19 Jun 2000 16:19:05 +1200 Message-ID: <67B808B0DD93D211ABEE0000B498356B02BCC0@internet.kbgroup.co.nz> From: Dave Preece To: freebsd-hackers@freebsd.org Subject: Quickie: C++ statically linked into kernel? MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 19 Jun 2000 16:26:45 +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm writing some C++ code that currently uses divert sockets off the firewall and for performance reasons moving the code kernel mode is looking like a (long term) good idea. The question is: Should I bite the bullet and start writing in pure C now (and therefore save pain later)? Can I just provide an API using extern "C" and link it in (with some calling functions in ipfw.c, of course)? Would an lkm be the best way to go? Cheers, Dave :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message