From: Michal Hocko <mhocko@kernel.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Mel Gorman <mgorman@suse.de>, Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net, skbuff: Get rid of unused skb_propagate_pfmemalloc
Date: Fri, 25 Sep 2015 16:11:08 +0200 [thread overview]
Message-ID: <20150925141108.GL16497@dhcp22.suse.cz> (raw)
In-Reply-To: <1440665197-23079-1-git-send-email-mhocko@kernel.org>
On Thu 27-08-15 10:46:37, mhocko@kernel.org wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> It seems that skb_propagate_pfmemalloc has never had a user since it was
> introduced by 0614002bb5f7 ("netvm: propagate page->pfmemalloc from
> skb_alloc_page to skb"). Remove it.
>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
> ---
> Hi,
> this has been noticed while working on 2f064f3485cd ("mm: make page
> pfmemalloc check more robust").
Has this just fallen through cracks or it is not interesting?
>
> include/linux/skbuff.h | 12 ------------
> 1 file changed, 12 deletions(-)
>
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index 9b88536487e6..9fcf69daa26c 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -2252,18 +2252,6 @@ static inline struct page *dev_alloc_page(void)
> }
>
> /**
> - * skb_propagate_pfmemalloc - Propagate pfmemalloc if skb is allocated after RX page
> - * @page: The page that was allocated from skb_alloc_page
> - * @skb: The skb that may need pfmemalloc set
> - */
> -static inline void skb_propagate_pfmemalloc(struct page *page,
> - struct sk_buff *skb)
> -{
> - if (page_is_pfmemalloc(page))
> - skb->pfmemalloc = true;
> -}
> -
> -/**
> * skb_frag_page - retrieve the page referred to by a paged fragment
> * @frag: the paged fragment
> *
> --
> 2.5.0
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2015-09-25 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 8:46 mhocko
2015-09-25 14:11 ` Michal Hocko [this message]
2016-10-19 12:32 Michal Hocko
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=20150925141108.GL16497@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
/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
all inboxes | Powered by JetHome®