| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 1 Dec 2006 01:07:04 -0800 (PST) From: tike64 <tike64@...oo.com> To: junjiec@...il.com Cc: linux-kernel@...r.kernel.org Subject: Re: realtime-preempt and arm > Hi, > > Without the support of High Resolution Timer > supported, the timer resolution wouldn't change. Ok, I understand that. I was not expecting more resolution. I expected only that I would get more precise 10ms delays. What confuses me is that the delays roughly doubled. > With high-resolution-timer supported, our > arm926-based board could get resolution like 40~50us. > There are codes you can reference ,may be you should > just try to implement it. It is good to know that the problem is not the arm architecture itself. Thanks to you for that. The problem must be in the lh7a40x specific code or my configuration. I am not yet convinced enough that high resolution timer implementation would solve the problem. I don't need timing resolution finer than 10ms providing that FB doesn't blow it up to 60ms. Could you or someone please give a hint where to look next or give an explanation why the lack of high resolution timer would behave like that. -- tike ____________________________________________________________________________________ Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists