From: Eric Dumazet <eric.dumazet@gmail.com>
To: Willem de Bruijn <willemb@google.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next] packet: packet fanout rollover during socket overload
Date: Thu, 14 Mar 2013 16:46:54 +0100 [thread overview]
Message-ID: <1363276014.29475.33.camel@edumazet-glaptop> (raw)
In-Reply-To: <CA+FuTScE_Y-waWVKRzJZuovbXdOmRQ3wHxjDETpjiwKwRvrbuQ@mail.gmail.com>
On Wed, 2013-03-13 at 12:13 -0400, Willem de Bruijn wrote:
> Will do. Apologies for the botched emails, including the html reply
> that the list thankfully rejected. I'll write some fanout
> documentation for the packet man page as penance.
Sounds good ! Thanks Willem !
prev parent reply other threads:[~2013-03-14 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 14:55 [PATCH net-next] packet: packet fanout rollover during socket overload Willem de Bruijn
2013-03-12 15:37 ` Willem de Bruijn
2013-03-13 14:25 ` Eric Dumazet
2013-03-13 15:51 ` Willem de Bruijn
2013-03-13 8:44 ` David Miller
2013-03-13 8:45 ` David Miller
2013-03-13 16:13 ` Willem de Bruijn
2013-03-14 15:46 ` Eric Dumazet [this message]
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=1363276014.29475.33.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--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