I think just writing them up anywhere will get at least some attention, because academics often do tend to search for "what is industry doing on this?", and they have less stringent standards for publication venues when they're looking for an industry paper versus an academic paper--- it doesn't have to be in the top conferences, since it's not a scientific result that needs to be peer reviewed so much as a documentation that industry is doing things in a certain way, and why they decided to do so.
Linux is starting to have a few self-run conferences that publish papers, like the annual GCC developers' conference, which might be good places for that sort of thing. Old-school Unix vendors traditionally had their own journals for that purpose, e.g. the DEC Technical Journal, Sun Technical Journal, and a whole host of IBM journals, all of which got cited in academia reasonably often.
The thing is, what the author describes is science. They implemented a bunch of different options, evaluated them experimentally, and came to conclusions. But, they just use their conclusions to inform how implementation should proceed, they didn't tell everyone else about their conclusions. Publishing those results would be interesting to academics.
Linux is starting to have a few self-run conferences that publish papers, like the annual GCC developers' conference, which might be good places for that sort of thing. Old-school Unix vendors traditionally had their own journals for that purpose, e.g. the DEC Technical Journal, Sun Technical Journal, and a whole host of IBM journals, all of which got cited in academia reasonably often.