Realtime Linux: academia v. reality [LWN.net]

Realtime Linux: academia v. reality

Posted Jul 28, 2010 6:06 UTC (Wed) by jmspeex (subscriber, #51639)
Parent article: Realtime Linux: academia v. reality

Research often tries to solve yesterday's problems over and over

I think at least part of the reason for that is the publication process. Between the time you actually do some work and the time it gets published, you can easily have 3 years, sometimes more. Most of that is due to the often painful and slow review process. On top of that, you have to consider that PhD students have to choose a topic early on and then stick to it. So if you spend 5 years working on a problem and then at the end you submit a paper paper that takes 3 years to get published, you end up with something that solves a problem as it was 8 years ago. Then of course you have the ones that *keep* working on problems that have become irrelevant.

(Log in to post comments)

Realtime Linux: academics kind of scarce!

Posted Jul 28, 2010 23:51 UTC (Wed) by alison (✭ supporter ✭, #63752) [Link]

The group I work in at Stanford Linear Accelerator Center is quite interested in real-time Linux and we've had a (long) series of meetings to discuss our strategy as we migrate at least in part from VxWorks/VME and RTEMS/m68K. My boss agreed with me that having a PhD or Master's student work on a related problem (say multicore scheduling) would be useful. I started poking around the conference proceedings looking for profs at UC Berkeley, Stanford, San Jose State or Santa Clara University to collaborate with, and I don't think there are any. As far as I can tell, there are no faculty interested in any aspect of Linux at these distinguished universities. That's sad given their histories. Is it a worrisome sign for Linux? I don't know, but certainly having local CS departments discussing Linux couldn't hurt. Industrial interest in Linux (including RT embedded) continues to grow locally.