From: "David S. Miller" <davem@redhat.com>
To: balbir.singh@wipro.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH]Small Minor optimization to kmem_cache_estimate
Date: Fri, 05 Oct 2001 16:44:41 -0700 (PDT) [thread overview]
Message-ID: <20011005.164441.08321186.davem@redhat.com> (raw)
In-Reply-To: <3BBD9ABD.6040909@wipro.com>
In-Reply-To: <3BBD9ABD.6040909@wipro.com>
From: "BALBIR SINGH" <balbir.singh@wipro.com>
Date: Fri, 05 Oct 2001 17:04:21 +0530
I verified the number of objects per slab is the same in both cases.
This patch may not improve the performance of your CPU by a great amount,
but when there is a faster way to do things, why live with the slower one.
Since this code only occurs during SLAB creation, you estimation on
CPU savings is correct.
Why live with it? Less changes to verify would be one reason :-)
Franks a lot,
David S. Miller
davem@redhat.com
prev parent reply other threads:[~2001-10-05 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 11:34 [RFC][PATCH]Small Minor optimization to kmem_cache_estimate BALBIR SINGH
2001-10-05 23:44 ` David S. Miller [this message]
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=20011005.164441.08321186.davem@redhat.com \
--to=davem@redhat.com \
--cc=balbir.singh@wipro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox