linux-kernel - Re: [take13 1/3] kevent: Core files.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 25 Aug 2006 00:01:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akpm@...l.org
Cc:	johnpol@....mipt.ru, hch@...radead.org,
	linux-kernel@...r.kernel.org, drepper@...hat.com,
	netdev@...r.kernel.org, zach.brown@...cle.com
Subject: Re: [take13 1/3] kevent: Core files.

From: Andrew Morton <akpm@...l.org>
Date: Thu, 24 Aug 2006 23:20:24 -0700

> On Fri, 25 Aug 2006 09:48:15 +0400
> Evgeniy Polyakov <johnpol@....mipt.ru> wrote:
> 
> > kmalloc is really slow actually - it always shows somewhere on top 
> > in profiles and brings noticeble overhead
> 
> It shouldn't.  Please describe the workload and send the profiles.

Not that I can account for the problem in this specific case, in my
experience cutting down kmalloc() calls matters a _lot_ performance
wise.

For example, this is why we allocate TCP sockets as one huge blob
instead of 3 seperate allocations (generic socket, IP socket, TCP
socket).

In fact, one of the remaining performance issues in IPSEC rule
creation is that we allocate seperately hunks of memory for the rule's
encryption state, the optional hash algorithm state, etc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/