Home » Mailing list archives » linux-netdev » 2008 » November » 11

Storing hardware timestamps - how about using the new skb's control block?

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Mark Smith <nanog@...>
To: <patrick.ohly@...>
Cc: <netdev@...>
Subject: Storing hardware timestamps - how about using the new skb's control block?
Date: Tuesday, November 11, 2008 - 4:53 pm

Hi,

Just a quick suggestion for storing hardware timestamps, how about
storing them in the new skb's control block?

From what I understand, any private users of the control block are
supposed to ignore the existing value, and if a protocol/tap is going
to be looking at the new skb, it should have done a skb_share_check()
first to grab it's own private copy if necessary, protecting the
control block stored timestamp value from any of the other skb
users who might change the control block value for their own purposes.

Regards,
Mark.

-- 

        "Sheep are slow and tasty, and therefore must remain constantly
         alert."
                                   - Bruce Schneier, "Beyond Fear"
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
Storing hardware timestamps - how about using the new skb's ..., Mark Smith, (Tue Nov 11, 4:53 pm)
Re: Storing hardware timestamps - how about using the new sk..., Patrick Ohly, (Wed Nov 12, 4:27 am)
Re: Storing hardware timestamps - how about using the new sk..., David Miller, (Wed Nov 12, 4:39 am)