From: linmiaohe <linmiaohe@huawei.com>
To: Eric Dumazet <edumazet@google.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"martin.varghese@nokia.com" <martin.varghese@nokia.com>,
Florian Westphal <fw@strlen.de>,
Pravin B Shelar <pshelar@ovn.org>,
Davide Caratti <dcaratti@redhat.com>,
Steffen Klassert <steffen.klassert@secunet.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"shmulik@metanetworks.com" <shmulik@metanetworks.com>,
"kyk.segfault@gmail.com" <kyk.segfault@gmail.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: Relax the npages test against MAX_SKB_FRAGS
Date: Wed, 19 Aug 2020 01:48:15 +0000 [thread overview]
Message-ID: <c6f895470c8c4c36ad1ed2c5ebfbe82c@huawei.com> (raw)
Eric Dumazet <edumazet@google.com> wrote:
>On Tue, Aug 18, 2020 at 4:58 AM Miaohe Lin <linmiaohe@huawei.com> wrote:
>>
>> The npages test against MAX_SKB_FRAGS can be relaxed if we succeed to
>> allocate high order pages as the note in comment said.
>>
>
>
>We do not want this change.
>
>This interface is used by datagram providers, we do not want to claim they can safely use skb allocations over 64KB.
>
>Returning -EMSGSIZE should not depend on availability of high-order pages.
>
>The comment was a hint, but we need first a valid user before considering expanding the interface.
I see. Many thanks for reply and explaination. :)
next reply other threads:[~2020-08-19 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 1:48 linmiaohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-18 11:57 Miaohe Lin
2020-08-18 14:15 ` Eric Dumazet
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=c6f895470c8c4c36ad1ed2c5ebfbe82c@huawei.com \
--to=linmiaohe@huawei.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=kyk.segfault@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=shmulik@metanetworks.com \
--cc=steffen.klassert@secunet.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
all inboxes | Powered by JetHome®