From: Octavian Purdila <opurdila@ixiacom.com>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [RFC][PATCH 1/3] net: per skb control messages
Date: Fri, 25 Jul 2008 01:12:03 +0300 [thread overview]
Message-ID: <200807250112.03379.opurdila@ixiacom.com> (raw)
In-Reply-To: <20080724.145600.30988015.davem@davemloft.net>
On Friday 25 July 2008, David Miller wrote:
> Traversing the list and maintaining the reference counting and sharing
> issues is expensive and error prone.
I've notice that :)
> We have a timestamp in the SKB already, why don't you simply override
> it when your feature is enable and set a single flag bit that
> indicates you used a HW timestamp to set that timestamp?
I thought of something similar, but I am not sure if I can to so, as it seems
that the skb->tstamp requires current gettimeofday semantics at least in
netfilter's ipt_time module.
Thanks,
tavi
next prev parent reply other threads:[~2008-07-24 22:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 22:01 [RFC][PATCH 0/3] net: per skb control messages Octavian Purdila
2008-07-23 22:01 ` [RFC][PATCH 1/3] " Octavian Purdila
2008-07-24 12:46 ` Herbert Xu
2008-07-24 13:34 ` Octavian Purdila
2008-07-24 15:01 ` Herbert Xu
2008-07-24 16:22 ` Octavian Purdila
2008-07-24 20:28 ` David Miller
2008-07-24 21:49 ` Octavian Purdila
2008-07-24 21:56 ` David Miller
2008-07-24 21:58 ` Stephen Hemminger
2008-07-24 22:35 ` Octavian Purdila
2008-07-24 23:05 ` Stephen Hemminger
2008-07-24 22:12 ` Octavian Purdila [this message]
2008-07-24 22:17 ` David Miller
2008-07-24 23:14 ` Octavian Purdila
2008-07-24 23:18 ` David Miller
2008-07-24 23:26 ` Octavian Purdila
2008-07-23 22:01 ` [RFC][PATCH 2/3] ip: support for SOL_SKB control messages for UDP/RAW sockets Octavian Purdila
2008-07-23 22:01 ` [RFC][PATCH 3/3] net: add SKB_SOL control messages Octavian Purdila
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200807250112.03379.opurdila@ixiacom.com \
--to=opurdila@ixiacom.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).