Re: time stamping 802.11n miniport tx packets
- From: "Pavel A." <pavel_a@xxxxxxxxxxxxxxx>
- Date: Sat, 1 Jul 2006 23:45:34 +0200
Why your adapter can't timestamp the packets?
It's internal clock may be be more precise than 16 ms.
--PA
"beninghaus" <beninghaus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:FFA3B515-A972-4B87-B1B9-63BF90BF0BEE@xxxxxxxxxxxxxxxx
I have been lead to believe from MS documentation that the
NdisGetCurrentSystemTime() function should be used to timestamp packets.
However the documentation also indicates that NdisGetCurrentSystemTime() is
only updated once every system tick. That implies to me between 10-16ms.
Yikes!
Do I have the wrong information about NdisGetCurrentSystemTime()?
I am working on an 802.11n miniport driver and I need to time stamp outgoing
packets when they arrive at the driver MiniportSendPackets() function.
This time stamp will later need to be calibrated to coincide with the timer
synchronization function (BEACON.TSF). TSF values are in the microsecond
range.
Can I use KeQueryPerformanceCounter() to get sub millisecond timestamps?
What is the best case resolution? In other words I'd like the incoming
packets to each have a unique timestamp and not the same value I could get
through NdisGetCurrentSystemTime().
Can a miniport driver make this call and still pass WHQL?
.
- Prev by Date: Re: Pool allocation question
- Next by Date: Is it possible to update a NDIS protocol driver programmatically?
- Previous by thread: Re: Pool allocation question
- Next by thread: Is it possible to update a NDIS protocol driver programmatically?
- Index(es):
Relevant Pages
|
|
