Re: cpuidle - minimum time for sleep
On Thu, 09 Oct 2014 21:28:23 +0300, Ran Shalit said: > Does anybody know what is the minimum expected time for sleep period > with the cpuidle ? Both processor dependent and sleep level dependent. There's a certain amount of latency induced by the hardware waking up. Look at /sys/devices/system/cpu/cpu*/cpuidle/state*/latency pgpBwupFkyQUv.pgp Description: PGP signature
Re: [PATCH 1/23] make section names compatible with -ffunction-sections -fdata-sections
On Wed, 02 Jul 2008 02:33:48 +0200, Denys Vlasenko said: > The purpose of these patches is to make kernel buildable > with "gcc -ffunction-sections -fdata-sections". > > Newer gcc and binutils can do dead code and data removal > at link time. It is achieved using combination of > -ffunction-sections -fdata-sections options for gcc and > --gc-sections for ld. Interesting idea. Do you happen to have before-and-after 'size vmlinux' numbers to show how much space is actually reclaimed? pgpoSIiQT4Jow.pgp Description: PGP signature
Re: [PATCH 1/3]: Replace kernel/timeconst.pl with kernel/timeconst.sh
On Sat, 03 Jan 2009 19:36:04 CST, Rob Landley said:
> On Saturday 03 January 2009 06:28:22 Ingo Oeser wrote:
> > > +for i in "MSEC 1000" "USEC 100"
> > > +do
> > > + NAME=$(echo $i | awk '{print $1}')
> >
> > cut -d' ' -f1 does the same
> >
> > > + PERIOD=$(echo $i | awk '{print $2}')
> >
> > cut -d' ' -f2 does the same
Close, but no cee-gar. cut does something counter-intuitive with multiple
blanks:
% echo 'ab' | awk '{print $2}'
b
% echo 'ab' | cut -d' ' -f2
% echo 'ab' | sed -r 's/[ ]+/ /g' | cut -d' ' -f2
b
Unfortunately, 'sed -r' isn't in the opengroup.org list of required options,
and sed 's/ / /g' doesn't DTRT for 3 or more blanks (as it won't recursively
apply the change to a *new* double blank formed by the previous change).
pgp9JlZUahVTQ.pgp
Description: PGP signature
Re: PATCH [0/3]: Simplify the kernel build by removing perl.
On Fri, 16 Jan 2009 00:11:09 CST, Rob Landley said: > P.S. I still hope autoconf dies off and the world wakes up and moves away > from that. And from makefiles for that matter. But in the meantime, I can > work around it with enough effort. What do you propose autoconf and makefiles get replaced by? % wc pidgin/configure* 34287 118303 1004074 pidgin/configure 24997684 81532 pidgin/configure.ac Which you rather code, 2.5K lines of autoconf or 35K lines of configure script? As long as there's enough diversity to require configure scripts, there's going to be a demand for an autoconf-ish feature to ease writing them. pgp2Iop0Uxq9b.pgp Description: PGP signature
