From: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: linux-mm@kvack.org, netdev@vger.kernel.org, davem@davemloft.net,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [net-next PATCH 1/6] net: Add skb_free_frag to replace use of put_page in freeing skb->head
Date: Wed, 6 May 2015 13:41:02 -0700 [thread overview]
Message-ID: <20150506134102.b01faad32e07ff3d308e1a09@linux-foundation.org> (raw)
In-Reply-To: <554A793F.3070001@redhat.com>
On Wed, 06 May 2015 13:27:43 -0700 Alexander Duyck <alexander.h.duyck@redhat.com> wrote:
> >> +void skb_free_frag(void *head)
> >> +{
> >> + struct page *page = virt_to_head_page(head);
> >> +
> >> + if (unlikely(put_page_testzero(page))) {
> >> + if (likely(PageHead(page)))
> >> + __free_pages_ok(page, compound_order(page));
> >> + else
> >> + free_hot_cold_page(page, false);
> >> + }
> >> +}
> > Why are we testing for PageHead in here? If the code were to simply do
> >
> > if (unlikely(put_page_testzero(page)))
> > __free_pages_ok(page, compound_order(page));
> >
> > that would still work?
>
> My assumption was that there was a performance difference between
> __free_pages_ok and free_hot_cold_page for order 0 pages. From what I
> can tell free_hot_cold_page will do bulk cleanup via free_pcppages_bulk
> while __free_pages_ok just calls free_one_page.
Could be. Plus there's hopefully some performance advantage if the
page is genuinely cache-hot. I don't think that anyone has verified
the benefits of the hot/cold optimisation in the last decade or two,
and it was always pretty marginal..
Is the PageHead thing really "likely"? We're usually dealing with
order>0 pages here?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-05-06 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 23:14 [net-next PATCH 0/6] Add skb_free_frag to replace put_page(virt_to_head_page(ptr)) Alexander Duyck
2015-05-04 23:14 ` [net-next PATCH 1/6] net: Add skb_free_frag to replace use of put_page in freeing skb->head Alexander Duyck
2015-05-05 0:16 ` Eric Dumazet
2015-05-05 2:49 ` Alexander Duyck
2015-05-06 19:38 ` Andrew Morton
2015-05-06 20:27 ` Alexander Duyck
2015-05-06 20:41 ` Andrew Morton [this message]
2015-05-06 20:55 ` Alexander Duyck
2015-05-04 23:14 ` [net-next PATCH 2/6] netcp: Replace put_page(virt_to_head_page(ptr)) w/ skb_free_frag Alexander Duyck
2015-05-04 23:14 ` [net-next PATCH 3/6] mvneta: " Alexander Duyck
2015-05-04 23:15 ` [net-next PATCH 4/6] e1000: Replace e1000_free_frag with skb_free_frag Alexander Duyck
2015-05-05 0:28 ` Jeff Kirsher
2015-05-04 23:15 ` [net-next PATCH 5/6] hisilicon: Replace put_page(virt_to_head_page()) with skb_free_frag() Alexander Duyck
2015-05-04 23:15 ` [net-next PATCH 6/6] bnx2x, tg3: " Alexander Duyck
2015-05-05 23:28 ` [net-next PATCH 0/6] Add skb_free_frag to replace put_page(virt_to_head_page(ptr)) David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-05-04 23:09 [net-next PATCH 1/6] net: Add skb_free_frag to replace use of put_page in freeing skb->head Alexander Duyck
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=20150506134102.b01faad32e07ff3d308e1a09@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alexander.h.duyck@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.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).