why does this need a JIT compiler?

Posted Apr 28, 2011 6:07 UTC (Thu) by dlang (guest, #313)
Parent article: A JIT for packet filters

my understanding of the definition of a JIT compiler is that the system starts to run the interpreted code and compiles it as it goes, then uses the compiled version in the future.

filters change very infrequently, so why do you need a JIT compiler instead of a normal compiler?

am I missing something on the definition here? or are they misusing the term JIT? or are they using a JIT setup when they could just as easily use a normal compiler?

why does this need a JIT compiler?

Posted May 21, 2011 12:00 UTC (Sat) by snemarch (guest, #75085) [Link] (2 responses)

JIT isn't a super precisely defined term.

In this context, the "just in time" means the code is not compiled into the kernel (or as a LKM), but generated from user data. You don't need the Java/.NET style "interpret until determined hotspot, then generate native" behavior in order to call something JIT :-)

why does this need a JIT compiler?

Posted Aug 17, 2011 2:42 UTC (Wed) by tao686 (guest, #77944) [Link] (1 responses)

I don't know if this JIT can avoid GPL licence? Since the filter sits on the userspace application, but finnally it is compiled and linked into kernel to execute. any idea on this? or it is a grey area, no one specify this?

From my point of view, this will not volidate the GPL licence. Linus can give some hint on this?

Also there is a trend, more and more code can be developed on userspace, such as UIO framework, it makes driver can be implemented in the userspace, this will avoid GPL licence issue. Then later on, more and more persons develop non-GPL licenced code, right?

why does this need a JIT compiler?

Posted Sep 29, 2011 13:54 UTC (Thu) by mcortese (guest, #52099) [Link]

I can hardly imagine why one should want to distribute his filters, be them interpreted, compiled, or JIT...