All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: Robert Shearman <rshearma@brocade.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] l3mdev: Improve use with main table
Date: Thu, 20 Apr 2017 08:25:37 -0600	[thread overview]
Message-ID: <dae262ea-681b-db1f-bc97-30f2e3c13aad@cumulusnetworks.com> (raw)
In-Reply-To: <256c2549-b831-2e7e-b18b-69243bb33ce3@brocade.com>

On 4/20/17 7:01 AM, Robert Shearman wrote:
>> The cached dst on sockets is one known place that causes a hang on a
>> delete. Basically the delete stalls until the sockets are closed. I have
>> a patch for sk_rx_dst which is the one I chased down last week.

I got to the bottom on the sk_rx_dst caching -- it is only a problem on
older kernels (e.g., our 4.1 kernels) and only with multicast udp
sockets. The early demux code in 4.1 is matching a listen socket when it
should not. The early demux code for mcast had some changes unrelated to
false matching that fixed the problem.

  reply	other threads:[~2017-04-20 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 14:21 [PATCH net-next 0/3] l3mdev: Improve use with main table Robert Shearman
2017-04-10 14:22 ` [PATCH net-next 1/3] ipv6: Fix route handling when using l3mdev set to " Robert Shearman
2017-04-10 14:22 ` [PATCH net-next 2/3] ipv4: " Robert Shearman
2017-04-10 14:22 ` [PATCH net-next 3/3] l3mdev: Fix lookup in local table when using " Robert Shearman
2017-04-12 16:51 ` [PATCH net-next 0/3] l3mdev: Improve use with " David Ahern
2017-04-13 12:48   ` Robert Shearman
2017-04-13 14:36     ` David Ahern
2017-04-20 13:01       ` Robert Shearman
2017-04-20 14:25         ` David Ahern [this message]
2017-04-20 22:36 ` David Ahern
2017-04-21 17:44   ` Robert Shearman
2017-04-21 20:47     ` David Ahern

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=dae262ea-681b-db1f-bc97-30f2e3c13aad@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rshearma@brocade.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.