From: Wolfram Sang <wsa@the-dreams.de>
To: Liguo Zhang <liguo.zhang@mediatek.com>
Cc: srv_heupstream@mediatek.com,
Matthias Brugger <matthias.bgg@gmail.com>,
Eddie Huang <eddie.huang@mediatek.com>,
Xudong Chen <xudong.chen@mediatek.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3] i2c: mediatek: i2c multi transfer optimization
Date: Tue, 12 Apr 2016 23:13:56 +0200 [thread overview]
Message-ID: <20160412211355.GA1526@katana> (raw)
In-Reply-To: <1457375031-3769-1-git-send-email-liguo.zhang@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
Hi,
thanks for the submission!
On Tue, Mar 08, 2016 at 02:23:51AM +0800, Liguo Zhang wrote:
> Signal complete() in the i2c irq handler after one transfer done,
> and then wait_for_completion_timeout() will return, this procedure
> may cost much time, so only signal complete() when the entire
> transaction has been completed, it will reduce the entire transaction
> time.
>
> Signed-off-by: Liguo Zhang <liguo.zhang@mediatek.com>
I wonder. You have less context switches, yes. On the other hand, you
likely have bigger interrupt latency because you do more stuff in the
interrupt handler. Is it really a gain in the end?
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] i2c: mediatek: i2c multi transfer optimization
Date: Tue, 12 Apr 2016 23:13:56 +0200 [thread overview]
Message-ID: <20160412211355.GA1526@katana> (raw)
In-Reply-To: <1457375031-3769-1-git-send-email-liguo.zhang@mediatek.com>
Hi,
thanks for the submission!
On Tue, Mar 08, 2016 at 02:23:51AM +0800, Liguo Zhang wrote:
> Signal complete() in the i2c irq handler after one transfer done,
> and then wait_for_completion_timeout() will return, this procedure
> may cost much time, so only signal complete() when the entire
> transaction has been completed, it will reduce the entire transaction
> time.
>
> Signed-off-by: Liguo Zhang <liguo.zhang@mediatek.com>
I wonder. You have less context switches, yes. On the other hand, you
likely have bigger interrupt latency because you do more stuff in the
interrupt handler. Is it really a gain in the end?
Regards,
Wolfram
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160412/d949e8c7/attachment.sig>
next prev parent reply other threads:[~2016-04-12 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 18:23 [PATCH v3] i2c: mediatek: i2c multi transfer optimization Liguo Zhang
2016-03-07 18:23 ` Liguo Zhang
2016-03-07 18:23 ` Liguo Zhang
2016-04-12 21:13 ` Wolfram Sang [this message]
2016-04-12 21:13 ` Wolfram Sang
2016-04-16 4:21 ` liguo zhang
2016-04-16 4:21 ` liguo zhang
2016-04-16 4:21 ` liguo zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160412211355.GA1526@katana \
--to=wsa@the-dreams.de \
--cc=eddie.huang@mediatek.com \
--cc=liguo.zhang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
--cc=xudong.chen@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.