On Wed, Feb 21, 2007 at 02:06:34PM +0300, Evgeniy Polyakov wrote: > Here is data for 50 bytes reading for essentially idle machine > (core duo 2.4 ghz): > > delta for syscall: 3326961404-3326969261: 7857 cycles = 3.273750 us Can you oprofile it too? -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- From: bert hubert <[email protected]>
- Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- From: Evgeniy Polyakov <[email protected]>
- Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- From: bert hubert <[email protected]>
- Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- From: Evgeniy Polyakov <[email protected]>
- Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- From: Evgeniy Polyakov <[email protected]>
- all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- Prev by Date: Re: [PATCH 3/4] coredump: ELF-FDPIC: enable to omit anonymous shared memory
- Next by Date: Re: current git crashes on bootup with pci_iounmap()
- Previous by thread: Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- Next by thread: Re: all syscalls initially taking 4usec on a P4? Re: nonblocking UDPv4 recvfrom() taking 4usec @ 3GHz?
- Index(es):
 |