From: Paulo Marques <pmarques@grupopie.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Gene Heskett <gene.heskett@verizon.net>, linux-kernel@vger.kernel.org
Subject: Re: OT: Why is usb data many times the cpu hog that firewire is?
Date: Wed, 23 Feb 2005 13:13:55 +0000 [thread overview]
Message-ID: <421C8193.2050808@grupopie.com> (raw)
In-Reply-To: <20050222231000.GA3163@waste.org>
Matt Mackall wrote:
>[...]
> JPEG data is DCT of 8x8 pixel chunks. If you can get at that, you can
> compare the DC terms of each chunk with minimal decoding. Various
> thumbnailers do this for speed already.
I really doubt that this would work. It seems to me that you can have
very different DC terms with very similar results. In other words, even
a little noise in the picture might produce very different DC terms.
Instead of comparing the DC terms, you could compare just the luminance.
You would have to decompress just half the data for that and you
wouldn't need to make the YUV->RGB conversion. That would probably save
a few cycles.
--
Paulo Marques - www.grupopie.com
All that is necessary for the triumph of evil is that good men do nothing.
Edmund Burke (1729 - 1797)
next prev parent reply other threads:[~2005-02-23 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 17:16 OT: Why is usb data many times the cpu hog that firewire is? Gene Heskett
2005-02-21 17:58 ` Oliver Neukum
2005-02-21 18:25 ` Gene Heskett
2005-02-21 18:29 ` Wichert Akkerman
2005-02-21 22:08 ` Gene Heskett
2005-02-22 23:10 ` Matt Mackall
2005-02-23 13:13 ` Paulo Marques [this message]
2005-02-23 17:15 ` Geert Uytterhoeven
2005-02-21 18:40 ` Paulo Marques
2005-02-21 18:46 ` Oliver Neukum
2005-02-24 11:52 ` David Ford
2005-02-22 8:53 ` Barry K. Nathan
2005-02-22 13:12 ` Gene Heskett
2005-02-23 23:28 ` Bill Davidsen
2005-02-24 23:50 ` H. Peter Anvin
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=421C8193.2050808@grupopie.com \
--to=pmarques@grupopie.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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