From: Richard Gobert <richardbgobert@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, aleksander.lobakin@intel.com,
lixiaoyan@google.com, lucien.xin@gmail.com,
richardbgobert@gmail.com, alexanderduyck@fb.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/1] gro: decrease size of CB
Date: Thu, 1 Jun 2023 18:09:28 +0200 [thread overview]
Message-ID: <20230601160924.GA9194@debian> (raw)
This patch frees up space in the GRO CB, which is currently at its maximum
size. This patch was submitted and reviewed previously in a patch series,
but is now reposted as a standalone patch, as suggested by Paolo.
(https://lore.kernel.org/netdev/889f2dc5e646992033e0d9b0951d5a42f1907e07.camel@redhat.com/)
Changelog:
v2 -> v3:
* add comment
v1 -> v2:
* remove inline keyword
Richard Gobert (1):
gro: decrease size of CB
include/net/gro.h | 26 ++++++++++++++++----------
net/core/gro.c | 19 ++++++++++++-------
2 files changed, 28 insertions(+), 17 deletions(-)
--
2.36.1
next reply other threads:[~2023-06-01 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 16:09 Richard Gobert [this message]
2023-06-01 16:14 ` [PATCH v3 1/1] gro: decrease size of CB Richard Gobert
2023-06-06 7:25 ` Eric Dumazet
2023-06-26 8:55 ` Gal Pressman
2023-06-27 14:21 ` David Ahern
2023-06-28 12:42 ` Gal Pressman
2023-06-28 14:19 ` David Ahern
2023-08-23 14:43 ` Gal Pressman
2023-08-24 3:31 ` David Ahern
2023-06-29 12:36 ` Richard Gobert
2023-06-29 13:04 ` Gal Pressman
2023-06-30 15:39 ` Richard Gobert
2023-07-02 14:41 ` Gal Pressman
2023-07-02 14:46 ` Gal Pressman
2023-07-03 14:23 ` Richard Gobert
2023-07-07 12:31 ` Richard Gobert
2023-07-09 6:55 ` Gal Pressman
2023-06-02 14:22 ` [PATCH v3 0/1] " Alexander Lobakin
2023-06-05 13:58 ` Richard Gobert
2023-06-06 13:24 ` Alexander Lobakin
2023-06-06 9:20 ` patchwork-bot+netdevbpf
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=20230601160924.GA9194@debian \
--to=richardbgobert@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.