From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next] tcp: Remove some spurious dropped packet profile hits from the passive connection accept path
Date: Thu, 20 Nov 2014 13:51:29 -0800 [thread overview]
Message-ID: <546E6261.700@hp.com> (raw)
In-Reply-To: <1416520109.8629.44.camel@edumazet-glaptop2.roam.corp.google.com>
On 11/20/2014 01:48 PM, Eric Dumazet wrote:
> On Thu, 2014-11-20 at 13:31 -0800, Rick Jones wrote:
>
>> Do you mean when there is actually data in the SYN?
>
> No, I mean the packet can be _dropped_ here, really.
>
> SYN flood for example.
Ah. I did not pick-up on that. Seeing the kfree_skb() in the original
code I thought it was the end of the line for the segment.
rick
prev parent reply other threads:[~2014-11-20 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 18:58 [PATCH net-next] tcp: Remove some spurious dropped packet profile hits from the passive connection accept path Rick Jones
2014-11-20 20:15 ` Vijay Subramanian
2014-11-20 20:47 ` Eric Dumazet
2014-11-20 21:31 ` Rick Jones
2014-11-20 21:48 ` Eric Dumazet
2014-11-20 21:51 ` Rick Jones [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=546E6261.700@hp.com \
--to=rick.jones2@hp.com \
--cc=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).