Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: Early TCP socket demux.
Date: Tue, 19 Jun 2012 06:31:11 +0200	[thread overview]
Message-ID: <1340080271.7491.2187.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120618.211539.105938285016510975.davem@davemloft.net>

On Mon, 2012-06-18 at 21:15 -0700, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>

> > This reminds the idea of having seperate dst per tcp socket, to remove
> > the dst refcnt contention as well.
> 
> I'm leery of this.
> 
> We're going to move towards having dst entries more strongly shared
> as we move to remove the routing cache.
> 
> In fact I have another short-term change planned that adjusts which
> keys the routing cache uses based upon what kinds of keys are actually
> active in the current FIB rule configuration.
> 
> I think we want to encourage sharing and make the route footprint
> smaller rather than expanding it's size artificually on even the
> socket level.
> 
> If you really care about this refcount problem, then it's another
> reason to never orphan socket sourced packets.  Then we wouldn't need
> to ever refcount the route just to send a packet, we'd just use the
> implicit reference held by the socket instead.  Socket route releasing
> would be held back by the presence of any packets in the socket send
> queue.  If we have to reset the dst mis-lifetime due to route flushes,
> we'd need to use a specific packet as a sequence point.
> 
> That to me sounds like a more reasonable approach than just making
> more and more routes.

We already don't touch dst refcnt on TCP xmit path, unless packet is
parked in Qdisc queue...

But with BQL this is becoming less effective.

  parent reply	other threads:[~2012-06-19  4:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  2:40 [PATCH] ipv4: Early TCP socket demux David Miller
2012-06-19  4:03 ` Stephen Hemminger
2012-06-19  4:10   ` David Miller
2012-06-19  4:13   ` Changli Gao
2012-06-19  4:16     ` David Miller
2012-06-19 18:31       ` Stephen Hemminger
2012-06-19  4:07 ` Eric Dumazet
2012-06-19  4:15   ` David Miller
2012-06-19  4:23     ` Eric Dumazet
2012-06-19  4:25       ` Eric Dumazet
2012-06-19  4:27         ` David Miller
2012-06-19  4:37           ` Eric Dumazet
2012-06-19  6:07             ` David Miller
2012-06-19  6:28               ` Eric Dumazet
2012-06-19  4:26       ` David Miller
2012-06-19  4:31     ` Eric Dumazet [this message]
2012-06-19  4:43 ` Changli Gao
2012-06-19  4:47   ` Eric Dumazet
2012-06-19  4:51     ` Changli Gao

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=1340080271.7491.2187.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --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