Re: [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes

Andrew Morton wrote:

What is the additional overhead, expressed in relative terms?  ie: as a percentage?

Short answer: ~3-4% in a not very scientific test.

Long answer: I timed 3 different runs of a program that created and then closed a pipe 10 million times on a patched and unpatched kernel. I then added up the

"system" times for each and divided them:

unpatched:
sys     1m53.959s
sys     1m56.083s
sys     1m48.055s

patched:
sys     1m56.899s
sys     1m57.027s
sys     1m57.031s

The result was 1.03803642150033866020.

-- Jeff
-
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/

---

• Follow-Ups:
  • Re: [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes
    • From: Eric Dumazet <[email protected]>

• References:
  • [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes
    • From: Jeff Layton <[email protected]>
  • Re: [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [RFC] Limit the size of the pagecache
• Next by Date: Re: 2.6.18-stable release plans?
• Previous by thread: Re: [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes
• Next by thread: Re: [PATCH 0/3] i_ino uniqueness: alternate approach -- hash the inodes
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]