All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Unai Uribarri <unai.uribarri@optenet.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets
Date: Thu, 9 Aug 2007 18:33:22 +0400	[thread overview]
Message-ID: <20070809143322.GA5345@2ka.mipt.ru> (raw)
In-Reply-To: <1186669314.24669.56.camel@localhost.localdomain>

On Thu, Aug 09, 2007 at 04:21:54PM +0200, Unai Uribarri (unai.uribarri@optenet.com) wrote:
> The attached patch removes the automatic timestamp activation, that
> only mmap'ed AF_PACKET sockets perform. I known it can break user
> applications, but I believe that it's the correct solution.

How tcpdump with mmap libpcap will work with it?

-- 
	Evgeniy Polyakov

  reply	other threads:[~2007-08-09 14:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 14:21 [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets Unai Uribarri
2007-08-09 14:33 ` Evgeniy Polyakov [this message]
2007-08-09 18:13   ` Unai Uribarri
2007-08-09 18:18     ` Evgeniy Polyakov
2007-08-09 18:44       ` Unai Uribarri
2007-08-10  8:34         ` Evgeniy Polyakov
2007-08-10 11:55           ` Unai Uribarri
2007-08-10 12:14             ` Evgeniy Polyakov
2007-08-09 18:50       ` Unai Uribarri
2007-09-13 10:42         ` [RFC] af_packet: allow disabling timestamps Stephen Hemminger
2007-09-13 12:24           ` Eric Dumazet
2007-09-14 10:26             ` Stephen Hemminger
2007-09-19  9:07               ` Evgeniy Polyakov
2007-09-27 14:08               ` Unai Uribarri
2007-09-27 14:34           ` Unai Uribarri
  -- strict thread matches above, loose matches on Subject: below --
2007-08-08 11:50 [PATCH 1/1] af_packet: don't enable timestamps in mmap'ed sockets Unai Uribarri

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=20070809143322.GA5345@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=unai.uribarri@optenet.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.