Pushing that init code into a separate function with no other changes will only add the overhead of the function call with no benefit. Remember that bcc is not a good compiler by modern standards (it's an ancient K&R C compiler with an ANSI prototype acceptance routine available and that performs limited optimizations) and it won't inline the function like gcc would, it'll just add bloat. When we get a compiler that is smarter, we can write more "proper" C code. For now some kernel configs already exceed the allowed 64K text segment size, so better to avoid such refactoring for now. There are many other places that need work more desperately. Try logging in as an invalid user at a login: prompt and login will never log in ever again, for example. On March 3, 2015 5:35:24 PM EST, Kirn Gill <segin2005@xxxxxxxxx> wrote: >I was looking at the article yesterday with the release of 0.2.0. > >I'll see what I can do, the lack of an infobox on the article (that box >on >the right-hand side with release dates, version, license, etc) already >has >me an itch to go scratch... > >P.S. re: init_task, I still think the console init could use >refactoring. > >On Tue, Mar 3, 2015, 11:33 Jody Bruchon <jody@xxxxxxxxxxxxxxx> wrote: > >> http://en.wikipedia.org/wiki/ELKS >> >> The article has lots of outdated information for obvious reasons. >Would >> anyone here care to take a stab at fixing the article? I would do it >myself >> but I don't currently have time (and there's some more code that I >> discovered this morning which real needs my attention.) >> >> -Jody >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-8086" >in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
