On Fri, Nov 10, 2006 at 10:41:07AM -0700, Mark Maybee wrote:
> This looks fine. Note that the db_immediate_evict == 0 means that you
> will probably *not* see a callback to the pageout function immediately.
> This is the general case. We hold onto the znode (and related memory)
> until the associ
On Fri, Nov 10, 2006 at 06:36:07AM -0700, Mark Maybee wrote:
> Pawel Jakub Dawidek wrote:
> >On Tue, Nov 07, 2006 at 06:06:48PM -0700, Mark Maybee wrote:
> >>The problem is that in ZFS the vnode holds onto more memory than just
> >>the vnode itself. Its fine to place the vnode on a "free vnodes li
On Tue, Nov 07, 2006 at 06:06:48PM -0700, Mark Maybee wrote:
> The problem is that in ZFS the vnode holds onto more memory than just
> the vnode itself. Its fine to place the vnode on a "free vnodes list"
> after a VOP_INACTIVE()... but you need to make sure the you have
> "released" the *extra* m
Pawel Jakub Dawidek wrote:
> On Fri, Nov 10, 2006 at 06:36:07AM -0700, Mark Maybee wrote:
>
>>Pawel Jakub Dawidek wrote:
>>
>>>On Tue, Nov 07, 2006 at 06:06:48PM -0700, Mark Maybee wrote:
>>>
The problem is that in ZFS the vnode holds onto more memory than just
the vnode itself. Its fine
Pawel Jakub Dawidek wrote:
> On Tue, Nov 07, 2006 at 06:06:48PM -0700, Mark Maybee wrote:
>
>>The problem is that in ZFS the vnode holds onto more memory than just
>>the vnode itself. Its fine to place the vnode on a "free vnodes list"
>>after a VOP_INACTIVE()... but you need to make sure the you
Pawel Jakub Dawidek wrote:
> ZFS works really stable on FreeBSD, but I'm biggest problem is how to
> control ZFS memory usage. I've no idea how to leash that beast.
>
> FreeBSD has a backpresure mechanism. I can register my function so it
> will be called when there are memory problems, which I do
Pawel Jakub Dawidek wrote:
> ZFS works really stable on FreeBSD, but I'm biggest problem is how to
> control ZFS memory usage. I've no idea how to leash that beast.
>
> FreeBSD has a backpresure mechanism. I can register my function so it
> will be called when there are memory problems, which I do
> > Normally, even when memory is freed it is cached until
> > SLEEP memory allocation fails, and then it is
> > re-allocated. Is this your memory leak? So, memory
> > tends to so up as more and more allocated and never
> > decreased from a point, IMO.
>
> That's not the case
On Thu, Nov 02, 2006 at 12:16:31PM -0800, Erblichs wrote:
> Aawel Kakub Dawidek, et al,
>
> First, I am describing a moving target and maybe I
> am off target for you...
>
> The memory consumption output via slab allocator
> functions is not really correct.
>
> Nor
ZFS works really stable on FreeBSD, but I'm biggest problem is how to
control ZFS memory usage. I've no idea how to leash that beast.
FreeBSD has a backpresure mechanism. I can register my function so it
will be called when there are memory problems, which I do. I using it
for ARC layer.
Even with
sorry Pawel Jakub Dawidek,
I don't read what I type.. :-)
Mitchell Eeerblich
--
Erblichs wrote:
>
> Aawel Kakub Dawidek, et al,
>
> First, I am describing a moving target and maybe I
> am off target for you...
>
> The memory cons
Aawel Kakub Dawidek, et al,
First, I am describing a moving target and maybe I
am off target for you...
The memory consumption output via slab allocator
functions is not really correct.
Normally, even when memory is freed it is cached until
SLEEP
12 matches
Mail list logo
