netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: den@sw.ru
Cc: shemminger@linux-foundation.org, den@openvz.org,
	devel@openvz.org, netdev@vger.kernel.org,
	containers@lists.osdl.org
Subject: Re: [PATCH 1/4] netns: Tag the network flow with the network namespace it is in (v2)
Date: Wed, 05 Dec 2007 02:10:36 -0800 (PST)	[thread overview]
Message-ID: <20071205.021036.22032476.davem@davemloft.net> (raw)
In-Reply-To: <47559FA9.2080109@sw.ru>

From: "Denis V. Lunev" <den@sw.ru>
Date: Tue, 04 Dec 2007 21:42:49 +0300

> Stephen Hemminger wrote:
> > Can this be made conditional on network namespaces being configured on?
> > That way the flow structure won't have to grow taking more space.
> > It matters in DoS attacks where flow cache becomes a critical resource.
> 
> could you exactly point me out the flow cache your are talking about.
> Is this dst entry cache or struct flow_cache described in the
> net/core/flow.c
> 
> For the latter case, there is completely no difference in the size on my
> x86_64 host with SLAB allocator, i.e. there are 30 objects per slab
> with/without fl_net (objsize = 128).

This may be true, but another thing to consider is that flow
objects sit on the stack in many call sites.

I won't let this block your patch, but I want you to be cognizant
of this issue in the future, it's not all about SLAB.

You should also BTW consider how this change will effect D-cache
access patterns and L2 cache utilization.  Some object access
patterns may not fit in the cache, which did beforehand, which
can kill performance.  We're talking about something which gets
touched multiple times per packet at routing rates in the
million packet per second range.

  parent reply	other threads:[~2007-12-05 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04  9:53 [PATCH 1/4] netns: Tag the network flow with the network namespace it is in (v2) Denis V. Lunev
2007-12-04 14:26 ` Stephen Hemminger
2007-12-04 18:42   ` Denis V. Lunev
2007-12-04 22:40     ` Herbert Xu
2007-12-05  6:49       ` Denis V. Lunev
2007-12-05 10:10     ` David Miller [this message]
2007-12-05 10:13 ` David Miller

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=20071205.021036.22032476.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=containers@lists.osdl.org \
    --cc=den@openvz.org \
    --cc=den@sw.ru \
    --cc=devel@openvz.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).