[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150506134102.b01faad32e07ff3d308e1a09@linux-foundation.org>
Date: Wed, 6 May 2015 13:41:02 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexander Duyck <alexander.h.duyck@...hat.com>
Cc: linux-mm@...ck.org, netdev@...r.kernel.org, davem@...emloft.net,
Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [net-next PATCH 1/6] net: Add skb_free_frag to replace use of
put_page in freeing skb->head
On Wed, 06 May 2015 13:27:43 -0700 Alexander Duyck <alexander.h.duyck@...hat.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 from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists