Re: cpu-freq: running the perf increases the data rate?

2020-08-31 Thread Subhashini Rao Beerisetty
On Fri, Aug 28, 2020 at 6:04 PM Artem Bityutskiy wrote: > > On Thu, 2020-08-27 at 22:25 +0530, Subhashini Rao Beerisetty wrote: > > I have an application which finds the data rate over the PCIe > > interface. I’m getting the lesser data rate in one of my Linux X86 > >

cpu-freq: running the perf increases the data rate?

2020-08-27 Thread Subhashini Rao Beerisetty
[ Please keep me in CC as I'm not subscribed to the list] Hi all, I have an application which finds the data rate over the PCIe interface. I’m getting the lesser data rate in one of my Linux X86 systems. When I change the scaling_governor from "powersave" to "performance" mode for each CPU, then

Re: general protection fault vs Oops

2020-05-17 Thread Subhashini Rao Beerisetty
On Mon, May 18, 2020 at 2:16 AM Cong Wang wrote: > > On Sat, May 16, 2020 at 9:16 AM Subhashini Rao Beerisetty > wrote: > > Yes, those are out-of-tree modules. Basically, my question is, in > > general what is the difference between 'general protection fault' a

Re: general protection fault vs Oops

2020-05-16 Thread Subhashini Rao Beerisetty
On Sat, May 16, 2020 at 9:29 PM Randy Dunlap wrote: > > On 5/16/20 6:53 AM, Valdis Klētnieks wrote: > > On Sat, 16 May 2020 18:05:07 +0530, Subhashini Rao Beerisetty said: > > > >> In the first attempt when I run that test case I landed into “general > >

Re: general protection fault vs Oops

2020-05-16 Thread Subhashini Rao Beerisetty
On Sat, May 16, 2020 at 7:23 PM Valdis Klētnieks wrote: > > On Sat, 16 May 2020 18:05:07 +0530, Subhashini Rao Beerisetty said: > > > In the first attempt when I run that test case I landed into “general > > protection fault: [#1] SMP" .. Next I rebooted and ran t

general protection fault vs Oops

2020-05-16 Thread Subhashini Rao Beerisetty
Hi all, In my Linux box, I see that kernel crashes for a known test case. In the first attempt when I run that test case I landed into “general protection fault: [#1] SMP" .. Next I rebooted and ran the same test , but now it resulted the “Oops: 0002 [#1] SMP". In both cases the call trace l