netdev - Reclaiming memory for network interface

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>] [day] [month] [year] [list]

Message-ID: <d21a891b-514e-18e8-e5e6-0b6712e4236a@codeaurora.org>
Date:   Tue, 16 Oct 2018 09:36:08 -0700
From:   Sujeev Dias <sdias@...eaurora.org>
To:     unlisted-recipients:; (no To-header on input)
Cc:     netdev@...r.kernel.org, Tony Truong <truong@...eaurora.org>
Subject: Reclaiming memory for network interface

Hi

Setup: sdm845 connected to external modem over pcie interface

During a data call, we found out we spend more than 25% of cpu for 
memory ops with io coherency.  That include allocation, freeing, dma 
mapping, and unmapping.  As we pushing to higher data rate (beyond 7 
Gbps), the time we spend in memory operation is significant. So, we're 
looking into ways we can reclaim this memory.

One of idea we're thinking is:

1. allocate pages

2. Increment reference count of page

3. allocate skb, and assign page into paged data portion

4. Assign cb function to skb->destructor

5. once destructor get called, move the page to a new skb

Sound simple enough, but we couldn't find anyone actually doing this 
way.  Anything to be concern with above proposal? We see some example of 
using destructor to do deferred unmap but didn't see any example of 
re-using the buffer. Also, couldn't find any meaningful discussion about 
reclaiming memory for network data. Any thoughts on how we should solve 
this issue?  Any comment is welcome, thanks.

Sincerely

Sujeev

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project