|
|
Subscribe / Log in / New account

KS2009: How Google uses Linux

KS2009: How Google uses Linux

Posted Oct 21, 2009 21:57 UTC (Wed) by jmm82 (guest, #59425)
In reply to: KS2009: How Google uses Linux by cma
Parent article: KS2009: How Google uses Linux

I believe the reasons were outlined why they are not contributing code into the kernel.

1. They are not using kernels that are close to linus git head.
2. Some code would not be wanted in the mainline kernel.
3. Some code is not good enough to get into the mainline kernel.
4. They don't want to have 30 people saying the code will only get in if it does this. Aka. They don't want to make it support the features they are not using.
5. Some code is proprietary and they want to protect the IP. As was stated above as long as they are not distributing the code the changes are their property.
6. A lot of there patches are code backported from mainline, so it is already in the kernel.

I think moving forward that you will see Google have a few developers working on mainline to try and influence future kernels because it will be financially cheaper to carry as few patches as possible. Also, I feel they will always have some patches that they feel are too valuable IP to gave back and will continue to maintain those outside the mainline.


to post comments

KS2009: How Google uses Linux

Posted Oct 21, 2009 22:46 UTC (Wed) by cpeterso (guest, #305) [Link]

If Google simply made their (non-proprietary) patches or git trees available to the public, then other kernel developers could adapt (or be inspired by) Google's work to the mainline kernel.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds