From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] net: sk_drops consolidation
Date: Wed, 14 Oct 2009 20:40:21 -0700 (PDT) [thread overview]
Message-ID: <20091014.204021.97690983.davem@davemloft.net> (raw)
In-Reply-To: <4AD68D4C.2080108@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 15 Oct 2009 04:47:40 +0200
> sock_queue_rcv_skb() can update sk_drops itself, removing need for
> callers to take care of it. This is more consistent since
> sock_queue_rcv_skb() also reads sk_drops when queueing a skb.
>
> This adds sk_drops managment to many protocols that not cared yet.
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Looks great, applied.
next prev parent reply other threads:[~2009-10-15 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 2:47 [PATCH net-next-2.6] net: sk_drops consolidation Eric Dumazet
2009-10-15 3:40 ` David Miller [this message]
2009-10-15 10:12 ` [PATCH net-next-2.6] net: sk_drops consolidation part 2 Eric Dumazet
2009-10-19 1:54 ` David Miller
2009-10-15 7:43 ` [PATCH net-next-2.6] net: sk_drops consolidation Rémi Denis-Courmont
2009-10-15 10:20 ` Eric Dumazet
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=20091014.204021.97690983.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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 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).