CCed: Paolo Bonzini
On Fri, Oct 16, 2020 at 1:53 PM Minchan Kim wrote:
[snip]
> > And there might be others, and adding everything to /proc/meminfo is not
> > feasible. I have once proposed adding a counter called "Unaccounted:" which
> > would at least tell the user easily if a significant porti
On Fri, Oct 16, 2020 at 05:38:26PM +0200, Vlastimil Babka wrote:
> On 10/13/20 10:09 AM, Mike Rapoport wrote:
> > > We are not complaining about TCP using too much memory, but how do
> > > we know that TCP uses a lot of memory. When I firstly face this problem,
> > > I do not know who uses the 25GB
On 10/13/20 10:09 AM, Mike Rapoport wrote:
We are not complaining about TCP using too much memory, but how do
we know that TCP uses a lot of memory. When I firstly face this problem,
I do not know who uses the 25GB memory and it is not shown in the /proc/meminfo.
If we can know the amount memory
On Tue, Oct 13, 2020 at 08:21:13AM -0700, Randy Dunlap wrote:
> On 10/13/20 8:12 AM, Mike Rapoport wrote:
> > On Tue, Oct 13, 2020 at 07:43:59AM -0700, Randy Dunlap wrote:
> >> On 10/13/20 1:09 AM, Mike Rapoport wrote:
> >>> On Mon, Oct 12, 2020 at 05:53:01PM +0800, Muchun Song wrote:
> On Mon
On Tue, Oct 13, 2020 at 4:09 PM Mike Rapoport wrote:
>
> On Mon, Oct 12, 2020 at 05:53:01PM +0800, Muchun Song wrote:
> > On Mon, Oct 12, 2020 at 5:24 PM Eric Dumazet wrote:
> > >
> > > On 10/12/20 10:39 AM, Muchun Song wrote:
> > > > On Mon, Oct 12, 2020 at 3:42 PM Eric Dumazet
> > > > wrote:
On 10/13/20 8:12 AM, Mike Rapoport wrote:
> On Tue, Oct 13, 2020 at 07:43:59AM -0700, Randy Dunlap wrote:
>> On 10/13/20 1:09 AM, Mike Rapoport wrote:
>>> On Mon, Oct 12, 2020 at 05:53:01PM +0800, Muchun Song wrote:
On Mon, Oct 12, 2020 at 5:24 PM Eric Dumazet
wrote:
>
> On 10/1
On Tue, Oct 13, 2020 at 07:43:59AM -0700, Randy Dunlap wrote:
> On 10/13/20 1:09 AM, Mike Rapoport wrote:
> > On Mon, Oct 12, 2020 at 05:53:01PM +0800, Muchun Song wrote:
> >> On Mon, Oct 12, 2020 at 5:24 PM Eric Dumazet
> >> wrote:
> >>>
> >>> On 10/12/20 10:39 AM, Muchun Song wrote:
> On M
On 10/13/20 1:09 AM, Mike Rapoport wrote:
> On Mon, Oct 12, 2020 at 05:53:01PM +0800, Muchun Song wrote:
>> On Mon, Oct 12, 2020 at 5:24 PM Eric Dumazet wrote:
>>>
>>> On 10/12/20 10:39 AM, Muchun Song wrote:
On Mon, Oct 12, 2020 at 3:42 PM Eric Dumazet wrote:
>
> On Mon, Oct 12, 202
On Mon, Oct 12, 2020 at 05:53:01PM +0800, Muchun Song wrote:
> On Mon, Oct 12, 2020 at 5:24 PM Eric Dumazet wrote:
> >
> > On 10/12/20 10:39 AM, Muchun Song wrote:
> > > On Mon, Oct 12, 2020 at 3:42 PM Eric Dumazet wrote:
> > >>
> > >> On Mon, Oct 12, 2020 at 6:22 AM Muchun Song
> > >> wrote:
>
On 10/12/20 11:53 AM, Muchun Song wrote:
> We are not complaining about TCP using too much memory, but how do
> we know that TCP uses a lot of memory. When I firstly face this problem,
> I do not know who uses the 25GB memory and it is not shown in the
> /proc/meminfo.
> If we can know the amo
On Tue, Oct 13, 2020 at 6:12 AM Cong Wang wrote:
>
> On Mon, Oct 12, 2020 at 2:53 AM Muchun Song wrote:
> > We are not complaining about TCP using too much memory, but how do
> > we know that TCP uses a lot of memory. When I firstly face this problem,
> > I do not know who uses the 25GB memory an
On Tue, Oct 13, 2020 at 5:47 AM Cong Wang wrote:
>
> On Sun, Oct 11, 2020 at 9:22 PM Muchun Song wrote:
> >
> > On Mon, Oct 12, 2020 at 2:39 AM Cong Wang wrote:
> > >
> > > On Sat, Oct 10, 2020 at 3:39 AM Muchun Song
> > > wrote:
> > > >
> > > > The amount of memory allocated to sockets buffer
On Mon, Oct 12, 2020 at 2:53 AM Muchun Song wrote:
> We are not complaining about TCP using too much memory, but how do
> we know that TCP uses a lot of memory. When I firstly face this problem,
> I do not know who uses the 25GB memory and it is not shown in the
> /proc/meminfo.
> If we can know
On Sun, Oct 11, 2020 at 9:22 PM Muchun Song wrote:
>
> On Mon, Oct 12, 2020 at 2:39 AM Cong Wang wrote:
> >
> > On Sat, Oct 10, 2020 at 3:39 AM Muchun Song
> > wrote:
> > >
> > > The amount of memory allocated to sockets buffer can become significant.
> > > However, we do not display the amount
On Mon, Oct 12, 2020 at 5:24 PM Eric Dumazet wrote:
>
>
>
> On 10/12/20 10:39 AM, Muchun Song wrote:
> > On Mon, Oct 12, 2020 at 3:42 PM Eric Dumazet wrote:
> >>
> >> On Mon, Oct 12, 2020 at 6:22 AM Muchun Song
> >> wrote:
> >>>
> >>> On Mon, Oct 12, 2020 at 2:39 AM Cong Wang
> >>> wrote:
> >
On 10/12/20 10:39 AM, Muchun Song wrote:
> On Mon, Oct 12, 2020 at 3:42 PM Eric Dumazet wrote:
>>
>> On Mon, Oct 12, 2020 at 6:22 AM Muchun Song wrote:
>>>
>>> On Mon, Oct 12, 2020 at 2:39 AM Cong Wang wrote:
On Sat, Oct 10, 2020 at 3:39 AM Muchun Song
wrote:
>
> The
On Mon, Oct 12, 2020 at 3:42 PM Eric Dumazet wrote:
>
> On Mon, Oct 12, 2020 at 6:22 AM Muchun Song wrote:
> >
> > On Mon, Oct 12, 2020 at 2:39 AM Cong Wang wrote:
> > >
> > > On Sat, Oct 10, 2020 at 3:39 AM Muchun Song
> > > wrote:
> > > >
> > > > The amount of memory allocated to sockets buf
On Mon, Oct 12, 2020 at 6:22 AM Muchun Song wrote:
>
> On Mon, Oct 12, 2020 at 2:39 AM Cong Wang wrote:
> >
> > On Sat, Oct 10, 2020 at 3:39 AM Muchun Song
> > wrote:
> > >
> > > The amount of memory allocated to sockets buffer can become significant.
> > > However, we do not display the amount
On Mon, Oct 12, 2020 at 2:39 AM Cong Wang wrote:
>
> On Sat, Oct 10, 2020 at 3:39 AM Muchun Song wrote:
> >
> > The amount of memory allocated to sockets buffer can become significant.
> > However, we do not display the amount of memory consumed by sockets
> > buffer. In this case, knowing where
On Sat, Oct 10, 2020 at 3:39 AM Muchun Song wrote:
>
> The amount of memory allocated to sockets buffer can become significant.
> However, we do not display the amount of memory consumed by sockets
> buffer. In this case, knowing where the memory is consumed by the kernel
We do it via `ss -m`. Is
On Sun, Oct 11, 2020 at 9:53 PM Mike Rapoport wrote:
>
> On Sat, Oct 10, 2020 at 06:38:54PM +0800, Muchun Song wrote:
> > The amount of memory allocated to sockets buffer can become significant.
> > However, we do not display the amount of memory consumed by sockets
> > buffer. In this case, knowi
On Sat, Oct 10, 2020 at 06:38:54PM +0800, Muchun Song wrote:
> The amount of memory allocated to sockets buffer can become significant.
> However, we do not display the amount of memory consumed by sockets
> buffer. In this case, knowing where the memory is consumed by the kernel
> is very difficul
On Sun, Oct 11, 2020 at 12:37 AM Randy Dunlap wrote:
>
> Hi,
>
> On 10/10/20 3:38 AM, Muchun Song wrote:
> > The amount of memory allocated to sockets buffer can become significant.
> > However, we do not display the amount of memory consumed by sockets
> > buffer. In this case, knowing where the
The amount of memory allocated to sockets buffer can become significant.
However, we do not display the amount of memory consumed by sockets
buffer. In this case, knowing where the memory is consumed by the kernel
is very difficult. On our server with 500GB RAM, sometimes we can see
25GB disappear
Hi,
On 10/10/20 3:38 AM, Muchun Song wrote:
> The amount of memory allocated to sockets buffer can become significant.
> However, we do not display the amount of memory consumed by sockets
> buffer. In this case, knowing where the memory is consumed by the kernel
> is very difficult. On our server
25 matches
Mail list logo
