From: Jakub Kicinski <kuba@kernel.org>
To: Shinas Rasheed <srasheed@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<hgani@marvell.com>, <vimleshk@marvell.com>, <egallen@redhat.com>,
<mschmidt@redhat.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<davem@davemloft.net>, <wizhao@redhat.com>, <konguyen@redhat.com>,
"Veerasenareddy Burru" <vburru@marvell.com>,
Sathesh Edara <sedara@marvell.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next v2 1/4] octeon_ep: add padding for small packets
Date: Tue, 24 Oct 2023 17:15:04 -0700 [thread overview]
Message-ID: <20231024171504.568e28f0@kernel.org> (raw)
In-Reply-To: <20231024145119.2366588-2-srasheed@marvell.com>
On Tue, 24 Oct 2023 07:51:16 -0700 Shinas Rasheed wrote:
> Pad small packets to ETH_ZLEN before transmit.
The commit message needs to focus on the "why", rather than "what".
--
pw-bot: cr
next prev parent reply other threads:[~2023-10-25 0:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 14:51 [PATCH net-next v2 0/4] Cleanup and optimizations to transmit code Shinas Rasheed
2023-10-24 14:51 ` [PATCH net-next v2 1/4] octeon_ep: add padding for small packets Shinas Rasheed
2023-10-25 0:15 ` Jakub Kicinski [this message]
2023-10-24 14:51 ` [PATCH net-next v2 2/4] octeon_ep: remove dma sync in trasmit path Shinas Rasheed
2023-10-24 14:51 ` [PATCH net-next v2 3/4] octeon_ep: implement xmit_more in transmit Shinas Rasheed
2023-10-25 0:21 ` Jakub Kicinski
2023-10-26 7:57 ` [EXT] " Shinas Rasheed
2023-10-26 8:28 ` Eric Dumazet
2023-10-26 14:44 ` Jakub Kicinski
2023-10-27 11:25 ` Shinas Rasheed
2023-10-28 6:38 ` David Laight
2023-10-30 14:14 ` Shinas Rasheed
2023-10-30 15:29 ` David Laight
2023-11-02 13:24 ` Shinas Rasheed
2023-10-24 14:51 ` [PATCH net-next v2 4/4] octeon_ep: remove atomic variable usage in Tx data path Shinas Rasheed
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=20231024171504.568e28f0@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=konguyen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vburru@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@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.