From: Davidlohr Bueso <dave@stgolabs.net>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: devel@driverdev.osuosl.org, eric@anholt.net,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH] staging: vc04_services: replace g_free_fragments_mutex with spinlock
Date: Mon, 28 Oct 2019 08:21:08 -0700 [thread overview]
Message-ID: <20191028152108.bjliafudxn3llysv@linux-p48b> (raw)
In-Reply-To: <576df522-f012-9dd1-9dcc-b7e444e82ac6@gmx.net>
On Mon, 28 Oct 2019, Stefan Wahren wrote:
>Hi Davidlohr,
>
>Am 27.10.19 um 23:15 schrieb Davidlohr Bueso:
>> There seems no need to be using a semaphore, or a sleeping lock
>> in the first place: critical region is extremely short, does not
>> call into any blocking calls and furthermore lock and unlocking
>> operations occur in the same context.
>>
>> Get rid of another semaphore user by replacing it with a spinlock.
>>
>> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
>> ---
>> This is in an effort to further reduce semaphore users in the kernel.
>>
>thanks for this. Could please also send this to devel@driverdev.osuosl.org?
Ccing.
>
>I only need to know, has this been tested on the Raspberry Pi?
No testing has been done, I have no hardware to test this.
Thanks,
Davidlohr
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next parent reply other threads:[~2019-10-28 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191027221530.12080-1-dave@stgolabs.net>
[not found] ` <576df522-f012-9dd1-9dcc-b7e444e82ac6@gmx.net>
2019-10-28 15:21 ` Davidlohr Bueso [this message]
2019-10-28 15:37 ` [PATCH] staging: vc04_services: replace g_free_fragments_mutex with spinlock Greg KH
2019-10-28 15:53 ` Davidlohr Bueso
2019-10-28 16:24 ` Greg KH
2019-10-28 16:35 ` Davidlohr Bueso
2019-10-28 16:59 ` Greg KH
2019-11-01 18:29 ` [PATCH resend] " Davidlohr Bueso
2019-11-02 10:33 ` Stefan Wahren
2019-11-02 10:35 ` Greg KH
2019-10-28 19:08 ` [PATCH] " Dan Carpenter
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=20191028152108.bjliafudxn3llysv@linux-p48b \
--to=dave@stgolabs.net \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wahrenst@gmx.net \
/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).