From: Benjamin Coddington <bcodding@redhat.com>
To: Pablo Silva <psilvao@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Fwd: NFS and Memory Buffers
Date: Mon, 15 Dec 2014 08:08:18 -0500 (EST) [thread overview]
Message-ID: <alpine.OSX.2.19.9992.1412150803320.1119@planck.local> (raw)
In-Reply-To: <CAF1in6QpHmj6Y3UurtZvjsvX2se3DqTWqNxVmYtd2i+xUnEVug@mail.gmail.com>
What you're doing does result in the cache being flushed, only to
immediately start to fill again.
I should have replied more to the point as Trond did: this is normal, do
not worry. Your memory is not being "used up", as the cache memory is given
back to the system if it is needed for other use.
Ben
On Mon, 15 Dec 2014, Pablo Silva wrote:
> Dear Benajmin;
>
> A colleague sent me this information as is, but the curious thing
> which does not release the memory buffer, except using the commands
> that you can appreciate.
>
> I am investigating if possible "know" that information is being stored
> there, and from what I see there is a command linux-fTools that could
> help me descubir the information being stored there, do not know if I
> bring in my analysis but it is my first step, I do not know if you
> have any other suggestions.
>
> grateful
>
> - Pablo
>
> On Mon, Dec 15, 2014 at 9:52 AM, Benjamin Coddington
> <bcodding@redhat.com> wrote:
> > Dear Pablo,
> >
> > Why are you restarting snmpd between flushing cache and reading
> > memory values? On a running system you can probably expect the
> > cache to immediately start to fill after a flush anyway.
> > y
> > Ben
> >
> > On Mon, 15 Dec 2014, Pablo Silva wrote:
> >
> >> Dear Readers:
> >>
> >> My boss has entrusted me to analyze why the memory buffers are
> >> not released a Linux server with Centos 6.4.?
> >>
> >> As informs me, the current reading is:
> >>
> >>
> >> [root@bck ~]# free -m
> >> total used free shared buffers cached
> >> Mem: 15936 15788 147 0 6746 438
> >> -/+ buffers/cache: 8604 7332
> >> Swap: 2047 0 2047
> >> [root@bck ~]#
> >> [root@bck ~]#
> >> [root@bck ~]# echo 3 > /proc/sys/vm/drop_caches && service snmpd
> >> restart && free -m
> >> Stopping snmpd: [ OK ]
> >> Starting snmpd: [ OK ]
> >> total used free shared buffers cached
> >> Mem: 15936 509 15426 0 93 16
> >> -/+ buffers/cache: 400 15536
> >> Swap: 2047 0 2047
> >> [root@bck ~]#
> >>
> >> I can not find the solution to release the memory buffer and cache
> >> memory so grateful for any hint for finding the solution to this
> >> "problem".
> >>
> >> -Paul
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
>
next prev parent reply other threads:[~2014-12-15 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF1in6QVkgyuC7VQ5QdYnYtPRJgArDwg5sXtKiAvyszCcQoZ-g@mail.gmail.com>
2014-12-15 12:25 ` Fwd: NFS and Memory Buffers Pablo Silva
2014-12-15 12:52 ` Benjamin Coddington
2014-12-15 12:57 ` Trond Myklebust
2014-12-15 13:02 ` Pablo Silva
2014-12-15 12:59 ` Pablo Silva
2014-12-15 13:08 ` Benjamin Coddington [this message]
2014-12-15 13:33 ` Pablo Silva
2014-12-15 13:40 ` Benjamin Coddington
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=alpine.OSX.2.19.9992.1412150803320.1119@planck.local \
--to=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=psilvao@gmail.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