netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: raise.sail@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] extend taskstats API to support networking accounts
Date: Thu, 23 Feb 2012 03:34:34 -0500 (EST)	[thread overview]
Message-ID: <20120223.033434.1801978370536071654.davem@davemloft.net> (raw)
In-Reply-To: <4F45F73F.3000708@gmail.com>

From: Li Yu <raise.sail@gmail.com>
Date: Thu, 23 Feb 2012 16:22:23 +0800

> This patch only records TCP/UDP/Raw-IP traffic so far, and adding
> other protocol support is easy.

It shouldn't even be necessary to put any code into specific
protocols, it should instead be done at some generic location
so that all protocols are supported transparently.

  reply	other threads:[~2012-02-23  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  8:22 [PATCH] extend taskstats API to support networking accounts Li Yu
2012-02-23  8:34 ` David Miller [this message]
2012-02-24  2:43   ` [PATCH net-next v2] " Li Yu
2012-02-24  3:05     ` Ben Hutchings
2012-02-24  3:15       ` Li Yu
2012-02-24 10:21   ` [PATCH net-next v3] " Li Yu
2012-02-26 19:14     ` 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=20120223.033434.1801978370536071654.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=raise.sail@gmail.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;
as well as URLs for NNTP newsgroup(s).