From: Cong Wang <xiyou.wangcong@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Michal Hocko <mhocko@kernel.org>,
Chas Williams <3chas3@gmail.com>,
Andrey Konovalov <andreyknvl@google.com>
Subject: Re: [Patch net] atm: remove an unnecessary loop
Date: Thu, 12 Jan 2017 16:14:30 -0800 [thread overview]
Message-ID: <CAM_iQpX2TipBW2Pm-OHRobfZaVoV9_D8Se8u9oKryt96SZFRkA@mail.gmail.com> (raw)
In-Reply-To: <20170113000700.GA1482@electric-eye.fr.zoreil.com>
On Thu, Jan 12, 2017 at 4:07 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Cong Wang <xiyou.wangcong@gmail.com> :
> [...]
>> diff --git a/net/atm/common.c b/net/atm/common.c
>> index a3ca922..7ec3bbc 100644
>> --- a/net/atm/common.c
>> +++ b/net/atm/common.c
>> @@ -72,10 +72,11 @@ static struct sk_buff *alloc_tx(struct atm_vcc *vcc, unsigned int size)
>> sk_wmem_alloc_get(sk), size, sk->sk_sndbuf);
>> return NULL;
>> }
>> - while (!(skb = alloc_skb(size, GFP_KERNEL)))
>> - schedule();
>> - pr_debug("%d += %d\n", sk_wmem_alloc_get(sk), skb->truesize);
>> - atomic_add(skb->truesize, &sk->sk_wmem_alloc);
>> + skb = alloc_skb(size, GFP_KERNEL);
>> + if (skb) {
>> + pr_debug("%d += %d\n", sk_wmem_alloc_get(sk), skb->truesize);
>> + atomic_add(skb->truesize, &sk->sk_wmem_alloc);
>> + }
>> return skb;
>> }
>
> Were alloc_skb moved one level up in the call stack, there would be
> no need to use the new wait api in the subsequent page, thus easing
> pre 3.19 longterm kernel maintenance (at least those on korg page).
alloc_skb(GFP_KERNEL) itself is sleeping, so the new wait api is still
needed.
next prev parent reply other threads:[~2017-01-13 0:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 5:02 [Patch net] atm: remove an unnecessary loop Cong Wang
2017-01-12 5:02 ` [Patch net] atm: switch to the new wait API for vcc_sendmsg() Cong Wang
2017-01-12 8:43 ` [Patch net] atm: remove an unnecessary loop Michal Hocko
2017-01-13 0:07 ` Francois Romieu
2017-01-13 0:14 ` Cong Wang [this message]
2017-01-13 13:23 ` Francois Romieu
2017-01-13 18:18 ` Cong Wang
2017-01-14 0:15 ` Francois Romieu
2017-01-14 0:41 ` Cong Wang
2017-01-13 17:10 ` David Miller
2017-01-13 18:20 ` Cong Wang
2017-01-13 23:54 ` Chas Williams
2017-01-14 0:30 ` Cong Wang
2017-01-14 11:34 ` Chas Williams
2017-01-14 0:14 ` Francois Romieu
2017-01-14 0:24 ` Francois Romieu
2017-01-14 0:36 ` Cong Wang
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=CAM_iQpX2TipBW2Pm-OHRobfZaVoV9_D8Se8u9oKryt96SZFRkA@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=3chas3@gmail.com \
--cc=andreyknvl@google.com \
--cc=mhocko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).