Messages in this thread | | | Date | Tue, 13 Jan 2004 15:43:48 -0800 | From | Andrew Morton <> | Subject | Re: Busy-wait delay in qmail 1.03 after upgrading to Linux 2.6 |
| |
Haakon Riiser <hakonrk@ulrik.uio.no> wrote: > > > Seems innocuous. What filesystem type is lock/trigger on? > > Reiserfs. > > > Can you generate a kernel profile of this activity? > > Done. Note that I had to reboot to do the profiling, so the > delay is not as bad as the first example: > > 344 00:19:07.476825 write(5, "\0", 1) = 1 <0.291500> > > Still around 700 times slower than 2.4 though. :-) Anyway, > here are the results: > > Output from time: > > real 0m0.309s > user 0m0.011s > sys 0m0.004s > > Data in prof.time:
OK, that's inconclusive. Could you do a few runs, or leave it a day or two, wait until the problem is really prominent and see if you can gather a clearer profile? The profiling overhead is negligible when profiling is enabled but not in use, so there is no need to reboot.
Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |