kernel coder writes: > Main idea of this project is to read packets from gigabit ethernet > card and get the required information from packets in less than 200 > cycles.The algorithem is so efficient that it will take less than 200 > cycles if ideal envoirnment is provided.Ideal envoirnment also means > that once data is brought into cache ,then it remains into cache till > packet processing is complete. OK. > I think root cause of sow many cycles might be the user space.As this > process is running in multitasking envoirment so there must always be > continuous process switching taking place .Timer interrupt must also > be disturbing the process.So i think in user space ,number of cycles > consumed must always be higher and inconsistent.What do you people > think ? You need to loop around the code that you're measuring. The overhead of your test is so great that it swamps the thing you're testing. Andrew.
