From: David Miller <davem@davemloft.net>
To: arnd@arndb.de
Cc: mlichvar@redhat.com, willemb@google.com, bjorn.topel@gmail.com,
gregkh@linuxfoundation.org, francisyyan@gmail.com,
edumazet@google.com, keescook@chromium.org, rami.rosen@intel.com,
andreyknvl@google.com, maloney@google.com,
sowmini.varadhan@oracle.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] [RFC v2] packet: experimental support for 64-bit timestamps
Date: Tue, 28 Nov 2017 15:08:15 -0500 (EST) [thread overview]
Message-ID: <20171128.150815.1752676303491956378.davem@davemloft.net> (raw)
In-Reply-To: <CAK8P3a0D++fwPCKOai-xFke6o6kBjS6XxdwB=+y5bVjr7rC6Ag@mail.gmail.com>
From: Arnd Bergmann <arnd@arndb.de>
Date: Tue, 28 Nov 2017 21:02:05 +0100
> Does this mean you think the general idea of an extended interface
> for 64-bit timestamps is useful for traditional packet sockets? I
> think that was still an open question, though we seem to be getting
> closer to consensus on the implementation and the interface that it
> should use if we want it.
If it can be done reasonably easy, which you patches seem to indicate
is the case, I have no objections to extending packet socket for
64-bit timestamps.
I hope that AF_CAPTURE will be designed in such a way that all apps
can migrate to it, and I will be making sure it is implemented
appropriately with that in mind.
But I don't think AF_CAPTURE should block your work here.
next prev parent reply other threads:[~2017-11-28 20:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 16:19 [PATCH 1/2] [net-next] packet: clarify timestamp overflow Arnd Bergmann
2017-11-27 16:19 ` [PATCH 2/2] [RFC] packet: experimental support for 64-bit timestamps Arnd Bergmann
2017-11-27 16:59 ` Jiri Pirko
2017-11-27 20:35 ` Willem de Bruijn
2017-11-27 20:51 ` Arnd Bergmann
2017-11-28 7:04 ` Björn Töpel
2017-11-28 8:46 ` Arnd Bergmann
2017-11-28 13:14 ` [PATCH] [RFC v2] " Arnd Bergmann
2017-11-28 14:24 ` Willem de Bruijn
2017-11-28 14:45 ` Arnd Bergmann
2017-11-28 15:05 ` David Miller
2017-11-28 20:02 ` Arnd Bergmann
2017-11-28 20:08 ` David Miller [this message]
2017-11-28 20:31 ` Arnd Bergmann
2017-11-28 20:32 ` [PATCH] [RFC v3] " Arnd Bergmann
2017-11-28 22:28 ` Willem de Bruijn
2017-11-29 12:31 ` Arnd Bergmann
2017-11-29 16:51 ` Willem de Bruijn
2017-11-29 20:06 ` Arnd Bergmann
2017-11-30 1:39 ` Willem de Bruijn
2017-11-30 1:54 ` Willem de Bruijn
2017-11-29 13:45 ` [PATCH] [RFC v4] " Arnd Bergmann
2017-11-28 14:08 ` [PATCH 2/2] [RFC] " Willem de Bruijn
2017-11-28 14:22 ` Arnd Bergmann
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=20171128.150815.1752676303491956378.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andreyknvl@google.com \
--cc=arnd@arndb.de \
--cc=bjorn.topel@gmail.com \
--cc=edumazet@google.com \
--cc=francisyyan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maloney@google.com \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rami.rosen@intel.com \
--cc=sowmini.varadhan@oracle.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®