lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55BB4F76.8090606@arm.com>
Date:	Fri, 31 Jul 2015 11:35:34 +0100
From:	Sudeep Holla <sudeep.holla@....com>
To:	Jassi Brar <jassisinghbrar@...il.com>
CC:	Sudeep Holla <sudeep.holla@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Juri Lelli <Juri.Lelli@....com>
Subject: Re: [PATCH 1/2] mailbox: switch to hrtimer for tx_complete polling



On 31/07/15 11:30, Jassi Brar wrote:
> On Fri, Jul 31, 2015 at 3:22 PM, Sudeep Holla <sudeep.holla@....com> wrote:
>>
>>>>
>>>> Again, sorry for misleading comment, we do need hrtimer as replied on
>>>> scpi thread. Any other concern with this patch ?
>>>>
>>> Polling by hrtimers is OK. Not to mean this is the best solution for
>>> your platform. Please revise the changelog completely.
>>>
>>
>> OK, how about:
>>
>> "The mailbox core uses jiffy based timer to handle polling for the
>> transmit completion. If the client/protocol have/support notification
>> of the last packet transmit completion via ACK packet, then we tick the
>> Tx state machine immediately in the callback. However if the client
>> doesn't support that mechanism we might end-up waiting for atleast a
>> jiffy even though the remote is ready to receive the next request.
>>
>> This patch switches the timer used for that polling from jiffy-based
>> to hrtimer-based so that we can support polling at much higher time
>> resolution."
>
> Perfect.
>
Thanks, will respin the patches soon.

Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ