Hello,
I am writing ethernet network driver.
I would like to ask if there are any steps which can help when
debugging ethernet driver, or is it that the first test should already
involve transmit/recieve packets to/from ip stack ?
Any tips for debugging and testing a new ethernet driver will be
Did you tried ftrace? https://www.kernel.org/doc/Documentation/trace/ftrace.txt
I've been using this to measure some latencies. The problem here is
visualizing the output. If you need someting more elaborated than
simple prints with timestamps and delta calculations, then you should
try something
On Fri, Jul 29, 2016 at 9:05 PM, Daniel. wrote:
> Nice tool @Ricardo!
>
> 2016-07-29 10:48 GMT-03:00 Ricardo Ribalda Delgado
> :
>> you can use http://lttng.org/ for analyzing this
Thanks Ricardo, I will use this.
>>
>> Regards!
>>
>> On Fri,
Hello, that's an interesting question!
I'm currently reading the same book, but you've read more than me so far :)
On Mon, Aug 01, 2016 at 08:36:07AM +0300, Aleksander Alekseev wrote:
> * bogomips value (see `cat /proc/cpuinfo`) is determined only once
> during system boot
As far as I know, I
Hello
Currently I'm reading Linux Kernel Development, 3rd Edition by Robert
Love. Chapter 11 describes timers and udelay() procedure in
particular. According to the book (if I didn't get anything wrong):
* bogomips value (see `cat /proc/cpuinfo`) is determined only once
during system boot
*