From: Dipankar Sarma <dipankar@in.ibm.com>
To: Mala Anand <manand@us.ibm.com>
Cc: Bill Hartner <Bill_Hartner@us.ibm.com>,
linux-kernel@vger.kernel.org,
lse <lse-tech@lists.sourceforge.net>,
"Luck, Tony" <tony.luck@intel.com>
Subject: Re: [Lse-tech] [RFC] per cpu slab fix to reduce freemiss
Date: Thu, 1 Aug 2002 19:14:46 +0530 [thread overview]
Message-ID: <20020801191446.D32256@in.ibm.com> (raw)
In-Reply-To: <OF6D440764.727DFE3C-ON87256C08.0049B06D@boulder.ibm.com>; from manand@us.ibm.com on Thu, Aug 01, 2002 at 08:31:45AM -0500
On Thu, Aug 01, 2002 at 08:31:45AM -0500, Mala Anand wrote:
>
> Dipankar wrote..
> >Isn't it possible to tune the cpucache limit by writing to
> >/proc/slabinfo so that you avoid frequent draining of free objects ?
> >Am I missing something here ?
>
> Are you referring to raising the per cpu array limit? I don't think you
> tune that using /proc/slabinfo. However that does not solve the problem,
Hmm... then what does slabinfo_write()->kmem_tune_cpucache() do ?
> it only delays it. It needs to grow/shrink dynamically based on need. I
> am not only referring to frequently draining of free objects but also
> as a result of this refilling the object array due to subsequent
> allocations and so on.
If draining of free objects become rare, shouldn't refilling of the
object also become rare ?
Thanks
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-08-01 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 13:31 [Lse-tech] [RFC] per cpu slab fix to reduce freemiss Mala Anand
2002-08-01 13:44 ` Dipankar Sarma [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 21:31 Luck, Tony
2002-08-01 12:42 Mala Anand
2002-08-01 13:22 ` Dipankar Sarma
2002-07-30 16:20 Luck, Tony
2002-07-30 12:36 Mala Anand
2002-07-29 16:47 Luck, Tony
2002-07-27 2:29 Mala Anand
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=20020801191446.D32256@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=Bill_Hartner@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=manand@us.ibm.com \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox