<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">We see an continuous increase in slab
size of 1GB for slab cache named "size-16384" in a system. </font>
<br><font size=2 face="sans-serif">The system is stable and sending/receiving
bulk amounts of packets.</font>
<br>
<br><font size=2 face="sans-serif">"/proc/slabinfo" Initial Value:</font>
<br><font size=2 face="sans-serif">size-16384(DMA) 0 0 16384 1 4 : tunables
8 4 0 : slabdata 0 0 0</font>
<br><font size=2 face="sans-serif">size-16384 9247 9247 16384 1 4 : tunables
8 4 0 : slabdata 9247 9247 0</font>
<br>
<br><font size=2 face="sans-serif">"/proc/slabinfo" Final Value:</font>
<br><font size=2 face="sans-serif">size-16384(DMA) 0 0 16384 1 4 : tunables
8 4 0 : slabdata 0 0 0</font>
<br><font size=2 face="sans-serif">size-16384 75023 75023 16384 1 4 : tunables
8 4 0 : slabdata 75023 75023 0</font>
<br>
<br><font size=2 face="sans-serif">Can anyone please tell us what kind
of functions in kernel need to allocate an object for "size-16384"?</font>
<br><font size=2 face="sans-serif">In what possible scenarios are these
slab objects allocated?</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif">Sowmya</font><pre style="white-space:normal">=====-----=====-----=====<br>Notice: The information contained in this e-mail<br>message and/or attachments to it may contain <br>confidential or privileged information. If you are <br>not the intended recipient, any dissemination, use, <br>review, distribution, printing or copying of the <br>information contained in this e-mail message <br>and/or attachments to it are strictly prohibited. If <br>you have received this communication in error, <br>please notify us by reply e-mail or telephone and <br>immediately and permanently delete the message <br>and any attachments. Thank you<br><br><br></pre>