On 16/03/18 19:10, Evgeniy Didin wrote:
> Hello Adrian,
>
>> Yes. Unfortunately the clock used is not accurate enough to correctly order
>> the events across different CPUs, which makes it very hard to see delays
>> between requests. You could try a different clock - refer the --clockid
>> optio
Hello Adrian,
> Yes. Unfortunately the clock used is not accurate enough to correctly order
> the events across different CPUs, which makes it very hard to see delays
> between requests. You could try a different clock - refer the --clockid
> option to perf record.
>
> Nevertheless it shows the
On 15/03/18 17:08, Evgeniy Didin wrote:
> Hi Adrian,
>
>> On 14/03/18 14:32, Evgeniy Didin wrote:
>>> Hi Adrian,
>
> Was the performance affected? i.e. the results from bonnie++
I have run bonnie++ several times before and after mentioned commit. Here
is output:
--
On 15/03/18 19:21, Alexey Brodkin wrote:
> Hi Vineet,
>
> On Thu, 2018-03-15 at 09:38 -0700, Vineet Gupta wrote:
>> On 03/15/2018 02:27 AM, Adrian Hunter wrote:
>>> Please try:
>>>
>>> perf record -a -e mmc:* -- bonnie++ -u root -r 256 -s 512 -x 1 -d /mnt
>>>
>>> and share the resulting perf.d
Hi Vineet,
On Thu, 2018-03-15 at 09:38 -0700, Vineet Gupta wrote:
> On 03/15/2018 02:27 AM, Adrian Hunter wrote:
> > Please try:
> >
> > perf record -a -e mmc:* -- bonnie++ -u root -r 256 -s 512 -x 1 -d /mnt
> >
> > and share the resulting perf.data file when you are able
> > to reproduce th
On 03/15/2018 02:27 AM, Adrian Hunter wrote:
Please try:
perf record -a -e mmc:* -- bonnie++ -u root -r 256 -s 512 -x 1 -d /mnt
and share the resulting perf.data file when you are able
to reproduce the hung task message.
You may want to add this patch first:
https://marc.info/
On 14/03/18 14:32, Evgeniy Didin wrote:
> Hi Adrian,
>>>
>>> Was the performance affected? i.e. the results from bonnie++
>>
>> I have run bonnie++ several times before and after mentioned commit. Here is
>> output:
>> --<8---
Hi Adrian,
> >
> > Was the performance affected? i.e. the results from bonnie++
>
> I have run bonnie++ several times before and after mentioned commit. Here is
> output:
> --<8---
On Tue, 2018-03-13 at 16:05 +0200, Adrian Hunter wrote:
> On 13/03/18 14:04, Evgeniy Didin wrote:
> > Hello Adrian,
> >
> > I have discovered, that beggining with 4.16-rc1 bonnie++ benchmark
> > runs with errors on arc/hsdk board. After bisecting between 4.15 and
> > 4.16-rc1,
> > I have found th
On 13/03/18 14:04, Evgeniy Didin wrote:
> Hello Adrian,
>
> I have discovered, that beggining with 4.16-rc1 bonnie++ benchmark
> runs with errors on arc/hsdk board. After bisecting between 4.15 and 4.16-rc1,
> I have found that errors started after
> commit 81196976ed94 (mmc: block: Add blk-mq su
Hello Adrian,
I have discovered, that beggining with 4.16-rc1 bonnie++ benchmark
runs with errors on arc/hsdk board. After bisecting between 4.15 and 4.16-rc1,
I have found that errors started after
commit 81196976ed94 (mmc: block: Add blk-mq support).
Error message is like:
| # bonnie++ -u roo
11 matches
Mail list logo
