From: Andreas Oberritter <obi@linuxtv.org>
To: Marko Ristola <marko.ristola@kolumbus.fi>
Cc: "Mauro Carvalho Chehab" <mchehab@redhat.com>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Bjørn Mork" <bjorn@mork.no>
Subject: Re: Pending dvb_dmx_swfilter(_204)() patch tested enough
Date: Mon, 28 Mar 2011 14:07:25 +0200 [thread overview]
Message-ID: <4D9079FD.1060303@linuxtv.org> (raw)
In-Reply-To: <4D8E4AA2.7070408@kolumbus.fi>
Hello Marko,
On 03/26/2011 09:20 PM, Marko Ristola wrote:
> Following patch has been tested enough since last Summer 2010:
>
> "Avoid unnecessary data copying inside dvb_dmx_swfilter_204() function"
> https://patchwork.kernel.org/patch/118147/
> It modifies both dvb_dmx_swfilter_204() and dvb_dmx_swfilter() functions.
sorry, I didn't know about your patch. Can you please resubmit it with
the following changes?
- Don't use camelCase (findNextPacket)
- Remove disabled printk() calls.
- Only one statement per line.
if (unlikely(lost = pos - start)) {
while (likely((p = findNextPacket(buf, p, count, pktsize)) < count)) {
- Add white space between while and the opening brace.
while(likely(pos < count)) {
- Use unsigned data types for pos and pktsize:
static inline int findNextPacket(const u8 *buf, int pos, size_t count,
const int pktsize)
The CodingStyle[1] document can serve as a guideline on how to properly
format kernel code.
Does the excessive use of likely() and unlikely() really improve the
performance or is it just a guess?
Regards,
Andreas
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/CodingStyle
next prev parent reply other threads:[~2011-03-28 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 20:20 Pending dvb_dmx_swfilter(_204)() patch tested enough Marko Ristola
2011-03-28 12:07 ` Andreas Oberritter [this message]
2011-03-28 21:58 ` Mauro Carvalho Chehab
2011-03-29 21:38 ` Marko Ristola
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=4D9079FD.1060303@linuxtv.org \
--to=obi@linuxtv.org \
--cc=bjorn@mork.no \
--cc=linux-media@vger.kernel.org \
--cc=marko.ristola@kolumbus.fi \
--cc=mchehab@redhat.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.