netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sujeev Dias <sdias@codeaurora.org>
To: unlisted-recipients:; (no To-header on input)
Cc: netdev@vger.kernel.org, Tony Truong <truong@codeaurora.org>
Subject: Reclaiming memory for network interface
Date: Tue, 16 Oct 2018 09:36:08 -0700	[thread overview]
Message-ID: <d21a891b-514e-18e8-e5e6-0b6712e4236a@codeaurora.org> (raw)

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

                 reply	other threads:[~2018-10-17  0:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d21a891b-514e-18e8-e5e6-0b6712e4236a@codeaurora.org \
    --to=sdias@codeaurora.org \
    --cc=netdev@vger.kernel.org \
    --cc=truong@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).