linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: <yhchuang@realtek.com>
Cc: <linux-wireless@vger.kernel.org>, <jano.vesely@gmail.com>,
	<linux@endlessm.com>, <briannorris@chromium.org>,
	<gojun077@gmail.com>, <drake@endlessm.com>, <davem@davemloft.net>,
	<jian-hong@endlessm.com>
Subject: Re: [PATCH rebased 1/2] rtw88: pci: Move a mass of jobs in hw IRQ to soft IRQ
Date: Tue,  3 Sep 2019 13:37:04 +0000 (UTC)	[thread overview]
Message-ID: <20190903133704.408506083E@smtp.codeaurora.org> (raw)
In-Reply-To: <1567502047-24102-2-git-send-email-yhchuang@realtek.com>

<yhchuang@realtek.com> wrote:

> From: Jian-Hong Pan <jian-hong@endlessm.com>
> 
> There is a mass of jobs between spin lock and unlock in the hardware
> IRQ which will occupy much time originally. To make system work more
> efficiently, this patch moves the jobs to the soft IRQ (bottom half) to
> reduce the time in hardware IRQ.
> 
> Signed-off-by: Jian-Hong Pan <jian-hong@endlessm.com>
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>

2 patches applied to wireless-drivers-next.git, thanks.

b3d07736b30a rtw88: pci: Move a mass of jobs in hw IRQ to soft IRQ
79066903454b rtw88: pci: enable MSI interrupt

-- 
https://patchwork.kernel.org/patch/11127455/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2019-09-03 13:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  9:14 [PATCH rebased 0/2] rtw88: pci: interrupt routine improvement yhchuang
2019-09-03  9:14 ` [PATCH rebased 1/2] rtw88: pci: Move a mass of jobs in hw IRQ to soft IRQ yhchuang
2019-09-03 13:37   ` Kalle Valo [this message]
2019-09-03  9:14 ` [PATCH rebased 2/2] rtw88: pci: enable MSI interrupt yhchuang
2019-09-03 11:10 ` [PATCH rebased 0/2] rtw88: pci: interrupt routine improvement Kalle Valo
2019-09-03 11:55   ` Tony Chuang
2019-09-03 12:17     ` Kalle Valo
2019-09-03 12:21       ` Tony Chuang

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=20190903133704.408506083E@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=briannorris@chromium.org \
    --cc=davem@davemloft.net \
    --cc=drake@endlessm.com \
    --cc=gojun077@gmail.com \
    --cc=jano.vesely@gmail.com \
    --cc=jian-hong@endlessm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=yhchuang@realtek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).