My tuppence worth from a real-time embedded perspective:
A shorter time slice and other real-time improvements to the scheduler will
certainly improve life to the embedded crowd. Bear in mind that 90% of
processors are used for embedded apps. Shorter time slices etc. means
smaller buffers, less RAM and lower cost.
I don't know what the current distribution is for Linux regarding embedded
vs data processing, but the embedded use of Linux is certainly growing
rapidly - we expect to make a million thingummyjigs running Linux next year
and there are many other companies doing the same. Within the next few
years, I expect embedded use of Linux to overshadow data use by a large
margin.
Since embedded processors are 'invisible' and never in the news, I would be
very happy if Linus and others will keep us poor boys in mind...
-- Herman Oosthuysen Herman@WirelessNetworksInc.com Suite 300, #3016, 5th Ave NE, Calgary, Alberta, T2A 6K4, Canada Phone: (403) 569-5688, Fax: (403) 235-3965 ----- Original Message ----- > > Lets see: we have >1 GHz CPU and interrupts at >1000 Hz > => 1 Mcycle / interrupt - is that insane? > > If the hardware can support it? Why not let it? It is really up to the > applications/user to decide... > > > Raising that min_fragment thing from 5 to 10 would make the minimum DMA > > buffer go from 32 bytes to 1kB, which is a _lot_ more reasonable (what, > > at 2*2 bytes per sample and 44kHz would mean that a 1kB DMA buffer empties > > in less than 1/100th of a second, but at least it should be < 200 irqs/sec > > rather than >400). > > > > /RogerL > > -- > Roger Larsson > Skellefteċ > Sweden- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:16 EST