From: David Miller <davem@davemloft.net>
To: lirongqing@baidu.com
Cc: daniel@iogearbox.net, netdev@vger.kernel.org, tj@kernel.org,
ast@fb.com, brakmo@fb.com
Subject: Re: 答复: [PATCH][net-next] net: ip tos cgroup
Date: Thu, 19 Apr 2018 11:27:40 -0400 (EDT) [thread overview]
Message-ID: <20180419.112740.414437419078279622.davem@davemloft.net> (raw)
In-Reply-To: <2AD939572F25A448A3AE3CAEA61328C2375E35F6@BC-MAIL-M28.internal.baidu.com>
From: "Li,Rongqing" <lirongqing@baidu.com>
Date: Thu, 19 Apr 2018 04:56:09 +0000
> I think this method is easier to use than BPF, and more efficient
Ease of use is arguable, but for anything bpf this is going to
steadily improve over time therefore it is not much of an argument
against using bpf.
And I disagree on the efficient aspect as well.
next prev parent reply other threads:[~2018-04-19 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 3:36 [PATCH][net-next] net: ip tos cgroup Li RongQing
2018-04-17 14:11 ` Daniel Borkmann
2018-04-19 4:56 ` 答复: " Li,Rongqing
2018-04-19 15:27 ` David Miller [this message]
2018-04-25 21:39 ` kbuild test robot
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=20180419.112740.414437419078279622.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@fb.com \
--cc=brakmo@fb.com \
--cc=daniel@iogearbox.net \
--cc=lirongqing@baidu.com \
--cc=netdev@vger.kernel.org \
--cc=tj@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).