From: Kalle Valo <kvalo@codeaurora.org>
To: Avinash Patil <patila@marvell.com>
Cc: <linux-wireless@vger.kernel.org>, <akarwar@marvell.com>,
<cluo@marvell.com>, <liuzy@marvell.com>, <szli@marvell.com>,
Marc Yang <yangyang@marvell.com>
Subject: Re: [PATCH 1/4] mwifiex: avoid queue_work while work is ongoing
Date: Tue, 03 Mar 2015 14:37:50 +0200 [thread overview]
Message-ID: <87a8zu9rz5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1424883057-12102-2-git-send-email-patila@marvell.com> (Avinash Patil's message of "Wed, 25 Feb 2015 22:20:54 +0530")
Avinash Patil <patila@marvell.com> writes:
> From: Marc Yang <yangyang@marvell.com>
>
> Current code does not check whether main_work_queue or
> rx_work_queue is running when preparing to do queue_work,
> this code fix add check before calling queue_work, reducing
> unnecessary queue_work switch.
>
> This change instead sets more_task flag to ensure we run main_process
> superloop once again.
>
> Signed-off-by: Marc Yang <yangyang@marvell.com>
> Signed-off-by: Zhaoyang Liu <liuzy@marvell.com>
> Signed-off-by: Shengzhen Li <szli@marvell.com>
> Signed-off-by: Cathy Luo <cluo@marvell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> Signed-off-by: Avinash Patil <patila@marvell.com>
Really, it took six persons to write this patch? Or do you just dump the
same names to each patch?
> +void mwifiex_queue_main_work(struct mwifiex_adapter *adapter)
> +{
> + unsigned long flags;
> +
> + spin_lock_irqsave(&adapter->main_proc_lock, flags);
> + if (adapter->mwifiex_processing) {
> + adapter->more_task_flag = true;
> + spin_unlock_irqrestore(&adapter->main_proc_lock, flags);
> + } else {
> + spin_unlock_irqrestore(&adapter->main_proc_lock, flags);
> + queue_work(adapter->workqueue, &adapter->main_work);
> + }
> +}
> +EXPORT_SYMBOL_GPL(mwifiex_queue_main_work);
> +
> +static void mwifiex_queue_rx_work(struct mwifiex_adapter *adapter)
> +{
> + unsigned long flags;
> +
> + spin_lock_irqsave(&adapter->rx_proc_lock, flags);
> + if (adapter->rx_processing) {
> + spin_unlock_irqrestore(&adapter->rx_proc_lock, flags);
> + } else {
> + spin_unlock_irqrestore(&adapter->rx_proc_lock, flags);
> + queue_work(adapter->rx_workqueue, &adapter->rx_work);
> + }
> +}
I can apply this patch, but to me this looks like a horrible hack.
--
Kalle Valo
next prev parent reply other threads:[~2015-03-03 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 16:50 [PATCH 0/4] mwifiex: throughput enhancements for TX Avinash Patil
2015-02-25 16:50 ` [PATCH 1/4] mwifiex: avoid queue_work while work is ongoing Avinash Patil
2015-03-03 12:37 ` Kalle Valo [this message]
2015-03-05 6:38 ` Avinash Patil
2015-03-05 11:33 ` Kalle Valo
2015-03-05 11:39 ` Avinash Patil
2015-03-05 11:54 ` Kalle Valo
2015-02-25 16:50 ` [PATCH 2/4] mwifiex: get rid of BA setup helper functions Avinash Patil
2015-02-25 16:50 ` [PATCH 3/4] mwifiex: remove_bss_prio_lock Avinash Patil
2015-03-03 12:39 ` Kalle Valo
2015-02-25 16:50 ` [PATCH 4/4] mwifiex: preprocess packets from TX queue Avinash Patil
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=87a8zu9rz5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=liuzy@marvell.com \
--cc=patila@marvell.com \
--cc=szli@marvell.com \
--cc=yangyang@marvell.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.