On vie, 2007-09-14 at 12:26 +0200, Stephen Hemminger wrote:
> On Thu, 13 Sep 2007 14:24:06 +0200
> Eric Dumazet <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 13 Sep 2007 12:42:53 +0200
> > Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> >
> > > Currently, af_packet does not allow disabling timestamps.
This small modification to Stephen's patch timestamps the skb when
needed, so the timestamp can be reused by other af_packet sockets.
Signed-off-by: Unai Uribarri <[EMAIL PROTECTED]>
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -259,7 +259,8 @@ static void sock_disable_timestamp(struct sock *sk
On Fri, Sep 14, 2007 at 12:26:42PM +0200, Stephen Hemminger ([EMAIL PROTECTED])
wrote:
> No, then we end up timestamping all the packets, even if they get dropped by
> packet filter. The change in 2.6.24 allows dhclient (and rstp) to only call
> hires clock source for packets they want, not all pa
On Thu, 13 Sep 2007 14:24:06 +0200
Eric Dumazet <[EMAIL PROTECTED]> wrote:
> On Thu, 13 Sep 2007 12:42:53 +0200
> Stephen Hemminger <[EMAIL PROTECTED]> wrote:
>
> > Currently, af_packet does not allow disabling timestamps. This patch changes
> > that but doesn't force global timestamps on.
> >
>
On Thu, 13 Sep 2007 12:42:53 +0200
Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> Currently, af_packet does not allow disabling timestamps. This patch changes
> that but doesn't force global timestamps on.
>
> This shows up in bugzilla as:
> http://bugzilla.kernel.org/show_bug.cgi?id=4809
>
Currently, af_packet does not allow disabling timestamps. This patch changes
that but doesn't force global timestamps on.
This shows up in bugzilla as:
http://bugzilla.kernel.org/show_bug.cgi?id=4809
Patch against net-2.6.24 tree.
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
---
