From: Andi Kleen <ak@suse.de>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gigabit Performance 2.4.19-preX - Excessive locks, calls, waits
Date: 04 Mar 2002 09:28:21 +0100 [thread overview]
Message-ID: <p731yf03ffe.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20020304001223.A29448@vger.timpanogas.org.suse.lists.linux.kernel>
In-Reply-To: "Jeff V. Merkey"'s message of "4 Mar 2002 08:00:12 +0100"
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org> writes:
> /usr/src/linux/net/core/skbuff.c
>
> //int sysctl_hot_list_len = 128;
> int sysctl_hot_list_len = 1024; // bump this value up
>
The plan was to actually to get rid of the skb hot list. It was just
a stop gap solution to get CPU local smp allocation before Linux had
cpu local slab caches. The slab cache has been fixed and runs
cpu local now too, so there should be no need for it anymore as
the slab cache does essentially the same thing as the private hot list
cache (maintaining linked lists of objects and unlinking them quickly
on allocation and linking them again on free, all in O(1))
> alloc_skb_frame with fixed 1514 + fragment list allocations,
> sysctl_hot_list_len = 1024.
Something is bogus with your profile data. Increasing sysctl_hot_list_len
never changes the frequency with which kmalloc/kfree are called. All
it does is to produce less calls to kmem_cache_alloc() for the skb head,
but the skb data portion is always allocated using kmalloc(). Your
new profile doesn't show kmalloc so you changed something else.
-andi
next parent reply other threads:[~2002-03-04 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020304001223.A29448@vger.timpanogas.org.suse.lists.linux.kernel>
2002-03-04 8:28 ` Andi Kleen [this message]
2002-03-04 17:41 ` Gigabit Performance 2.4.19-preX - Excessive locks, calls, waits Jeff V. Merkey
2002-03-04 7:12 Jeff V. Merkey
2002-03-04 8:16 ` Andrew Morton
2002-03-04 15:04 ` Alan Cox
2002-03-04 17:46 ` Jeff V. Merkey
2002-03-04 18:34 ` Alan Cox
2002-03-04 21:02 ` Jeff V. Merkey
2002-03-04 17:39 ` Martin Josefsson
2002-03-04 18:04 ` Jeff V. Merkey
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=p731yf03ffe.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@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 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.