In message: <6ff30abd04102008163115a32d_at_mail.gmail.com> jamie rishaw at google mail <mitigator_at_gmail.com> writes: : What are the performance implications of a debug kernel? : : Disk space really shouldnt even be an issue.. if it is, and its down : to the difference of 20 megs, well, duno. 512 meg CF's going for : sub-$50 .. the only reason i could see even a debate would be any : significant performance hits.. So long as it can be turned off, I don't care too much. However, I'm going going to take exception that it isn't a disk space issue or that size doesn't matter. Size does matter. For a 64MB CF this would be a deal killer, and that's the size of the parts we're using now. With our X based systems, these cards are starting to fill up. In addition, we sometimes deploy new kernels to the field and 16MB takes a lot longer to upload than 3MB (think really bad connectivity to many of the remote locations our systems may be deployed in). I also have several machines where / is short on disk space, and I'd turn it off for them. It is simply too much extra to put on there. I could repartition these machines, but that's a huge pita and costs way too much in time and down time to do. The cost here isn't in disk space, but the hundreds or thousands of dollars of labor and/or opportunity costs. WarnerReceived on Wed Oct 20 2004 - 13:32:58 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:18 UTC