From: Daniel Borkmann <daniel@iogearbox.net>
To: Alexei Starovoitov <ast@plumgrid.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] ebpf: add helper for obtaining current processor id
Date: Fri, 13 Mar 2015 18:08:07 +0100 [thread overview]
Message-ID: <55031977.40408@iogearbox.net> (raw)
In-Reply-To: <55031933.6010507@plumgrid.com>
On 03/13/2015 06:06 PM, Alexei Starovoitov wrote:
...
> same comment as in other patch:
> could you rename it to BPF_FUNC_get_smp_processor_id ?
Will do, yep.
next prev parent reply other threads:[~2015-03-13 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 13:22 [PATCH net-next 0/2] eBPF updates Daniel Borkmann
2015-03-13 13:22 ` [PATCH net-next 1/2] ebpf: add prandom helper for packet sampling Daniel Borkmann
2015-03-13 16:58 ` Alexei Starovoitov
2015-03-13 17:03 ` Daniel Borkmann
2015-03-13 22:44 ` Daniel Borkmann
2015-03-13 22:53 ` Alexei Starovoitov
2015-03-14 0:11 ` Daniel Borkmann
2015-03-13 13:22 ` [PATCH net-next 2/2] ebpf: add helper for obtaining current processor id Daniel Borkmann
2015-03-13 17:06 ` Alexei Starovoitov
2015-03-13 17:08 ` Daniel Borkmann [this message]
2015-03-16 1:57 ` [PATCH net-next 0/2] eBPF updates David Miller
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=55031977.40408@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--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 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.