On 11/24/2017 7:00 PM, Vaneet Narang wrote:
> Hi Michal,
>
>>> We have been getting similar kind of such entries and eventually
>>> stackdepot reaches Max Cap. So we found this interface useful in debugging
>>> stackdepot issue so shared in community.
>
>> Then use it for internal debugging
On 11/24/2017 7:00 PM, Vaneet Narang wrote:
> Hi Michal,
>
>>> We have been getting similar kind of such entries and eventually
>>> stackdepot reaches Max Cap. So we found this interface useful in debugging
>>> stackdepot issue so shared in community.
>
>> Then use it for internal debugging
On Fri 24-11-17 13:30:25, Vaneet Narang wrote:
> Hi Michal,
>
> >> We have been getting similar kind of such entries and eventually
> >> stackdepot reaches Max Cap. So we found this interface useful in debugging
> >> stackdepot issue so shared in community.
>
> >Then use it for internal
On Fri 24-11-17 13:30:25, Vaneet Narang wrote:
> Hi Michal,
>
> >> We have been getting similar kind of such entries and eventually
> >> stackdepot reaches Max Cap. So we found this interface useful in debugging
> >> stackdepot issue so shared in community.
>
> >Then use it for internal
Hi Michal,
>> We have been getting similar kind of such entries and eventually
>> stackdepot reaches Max Cap. So we found this interface useful in debugging
>> stackdepot issue so shared in community.
>Then use it for internal debugging and provide a code which would scale
>better on smaller
Hi Michal,
>> We have been getting similar kind of such entries and eventually
>> stackdepot reaches Max Cap. So we found this interface useful in debugging
>> stackdepot issue so shared in community.
>Then use it for internal debugging and provide a code which would scale
>better on smaller
On Fri 24-11-17 11:57:07, Vaneet Narang wrote:
[...]
> > OK, so debugging a debugging facility... I do not think we want to
> > introduce a lot of code for something like that.
>
> We enabled stackdepot on our system and realised, in long run stack depot
> consumes
> more runtime memory then it
On Fri 24-11-17 11:57:07, Vaneet Narang wrote:
[...]
> > OK, so debugging a debugging facility... I do not think we want to
> > introduce a lot of code for something like that.
>
> We enabled stackdepot on our system and realised, in long run stack depot
> consumes
> more runtime memory then it
Hi Michal,
>> 5) To check number of entries in stackdepot to decide stackdepot hash size
>> for different systems.
>>For fewer entries hash table size can be reduced from 4MB.
>
> What are you going to do with that information. It is not like you can
> reduce the memory footprint or somehow
Hi Michal,
>> 5) To check number of entries in stackdepot to decide stackdepot hash size
>> for different systems.
>>For fewer entries hash table size can be reduced from 4MB.
>
> What are you going to do with that information. It is not like you can
> reduce the memory footprint or somehow
On Fri, Nov 24, 2017 at 10:54 AM, Michal Hocko wrote:
> On Fri 24-11-17 09:41:08, Maninder Singh wrote:
>> Hi Michal,
>>
>> > On Wed 22-11-17 16:17:41, Maninder Singh wrote:
>> > > This patch provides interface to check all the stack enteries
>> > > saved in stackdepot so far
On Fri, Nov 24, 2017 at 10:54 AM, Michal Hocko wrote:
> On Fri 24-11-17 09:41:08, Maninder Singh wrote:
>> Hi Michal,
>>
>> > On Wed 22-11-17 16:17:41, Maninder Singh wrote:
>> > > This patch provides interface to check all the stack enteries
>> > > saved in stackdepot so far as well as memory
On Fri 24-11-17 09:41:08, Maninder Singh wrote:
> Hi Michal,
>
> > On Wed 22-11-17 16:17:41, Maninder Singh wrote:
> > > This patch provides interface to check all the stack enteries
> > > saved in stackdepot so far as well as memory consumed by stackdepot.
> > >
> > > 1) Take current
On Fri 24-11-17 09:41:08, Maninder Singh wrote:
> Hi Michal,
>
> > On Wed 22-11-17 16:17:41, Maninder Singh wrote:
> > > This patch provides interface to check all the stack enteries
> > > saved in stackdepot so far as well as memory consumed by stackdepot.
> > >
> > > 1) Take current
Hi Michal,
> On Wed 22-11-17 16:17:41, Maninder Singh wrote:
> > This patch provides interface to check all the stack enteries
> > saved in stackdepot so far as well as memory consumed by stackdepot.
> >
> > 1) Take current depot_index and offset to calculate end address for one
> >
Hi Michal,
> On Wed 22-11-17 16:17:41, Maninder Singh wrote:
> > This patch provides interface to check all the stack enteries
> > saved in stackdepot so far as well as memory consumed by stackdepot.
> >
> > 1) Take current depot_index and offset to calculate end address for one
> >
On Wed 22-11-17 16:17:41, Maninder Singh wrote:
> This patch provides interface to check all the stack enteries
> saved in stackdepot so far as well as memory consumed by stackdepot.
>
> 1) Take current depot_index and offset to calculate end address for one
> iteration of
On Wed 22-11-17 16:17:41, Maninder Singh wrote:
> This patch provides interface to check all the stack enteries
> saved in stackdepot so far as well as memory consumed by stackdepot.
>
> 1) Take current depot_index and offset to calculate end address for one
> iteration of
This patch provides interface to check all the stack enteries
saved in stackdepot so far as well as memory consumed by stackdepot.
1) Take current depot_index and offset to calculate end address for one
iteration of (/sys/kernel/debug/depot_stack/depot_entries).
2) Fill end marker in
This patch provides interface to check all the stack enteries
saved in stackdepot so far as well as memory consumed by stackdepot.
1) Take current depot_index and offset to calculate end address for one
iteration of (/sys/kernel/debug/depot_stack/depot_entries).
2) Fill end marker in
20 matches
Mail list logo