|
|
|
Re: [PATCH 0/2] Fix 'already_tokenized()' performance problem | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Very nice patch. Simple and clean. Applied and pushed. On Tue, Apr 19, 2011 at 11:12 AM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > This series of two trivial patches makes 'already_tokenized()' go away > from profiles of a kernel build with C=2, shaving about 3-4% off the time > for me. I am suppressed that you can get 3-4% from just comparing the stream names. Last time I try to optimized that nextchar() and nextchar_slow() because Al complains the tab character force the slow path, I haven't seen some thing like 1% difference. So I leave it alone. Thanks for the patch. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Newbies FAQ] [Kernel List] [Site Home] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [Bugtraq] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [DDR & Rambus] [Trinity Fuzzer Tool]