> This example is done with a single threaded app.
> It is NOT NOT NOT intended to show any level of
> Thread-safe type coding.
>
> It is ONLY used to show that it is signifcantly lower cost
> to grab pre-allocated objects than to allocate the
> objects on dem
Group,
This example is done with a single threaded app.
It is NOT NOT NOT intended to show any level of
Thread-safe type coding.
It is ONLY used to show that it is signifcantly lower cost
to grab pre-allocated objects than to allocate the
objects o
On Thu, 5 Oct 2006, Erblichs wrote:
Casper Dik,
After my posting, I assumed that a code question should be
directed to the ZFS code alias, so I apologize to the people
show don't read code. However, since the discussion is here,
I will post a code proof here. Jus
Casper Dik,
After my posting, I assumed that a code question should be
directed to the ZFS code alias, so I apologize to the people
show don't read code. However, since the discussion is here,
I will post a code proof here. Just use "time program" to get
a g
On Wed, 4 Oct 2006, Erblichs wrote:
Casper Dik,
Yes, I am familiar with Bonwick's slab allocators and tried
it for wirespeed test of 64byte pieces for a 1Gb and then
100Mb Eths and lastly 10Mb Eth. My results were not
encouraging. I assume it has improved over ti
>Casper Dik,
>
> Yes, I am familiar with Bonwick's slab allocators and tried
> it for wirespeed test of 64byte pieces for a 1Gb and then
> 100Mb Eths and lastly 10Mb Eth. My results were not
> encouraging. I assume it has improved over time.
Nothing which tries to send 64
Casper Dik,
Yes, I am familiar with Bonwick's slab allocators and tried
it for wirespeed test of 64byte pieces for a 1Gb and then
100Mb Eths and lastly 10Mb Eth. My results were not
encouraging. I assume it has improved over time.
First, let me ask what ha
> at least one location:
>
> When adding a new dva node into the tree, a kmem_alloc is done with
> a KM_SLEEP argument.
>
> thus, this process thread could block waiting for memory.
>
> I would suggest adding a pre-allocated pool of dva nodes.
This is how the Solari
group,
at least one location:
When adding a new dva node into the tree, a kmem_alloc is done with
a KM_SLEEP argument.
thus, this process thread could block waiting for memory.
I would suggest adding a pre-allocated pool of dva nodes.
When a new
