From: =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?= <bjorn.topel@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH bpf-next 4/4] ixgbe, xsk: use XSK_NAPI_WEIGHT as NAPI poll budget
Date: Tue, 8 Sep 2020 13:12:12 +0200 [thread overview]
Message-ID: <0fb03a39-d098-8fc9-ba70-e919ef8e091e@intel.com> (raw)
In-Reply-To: <82901368-8e17-a63d-0e46-2434b5777c04@molgen.mpg.de>
On 2020-09-08 12:12, Paul Menzel wrote:
> Dear Bj?rn,
>
>
> Am 07.09.20 um 17:02 schrieb Bj?rn T?pel:
>> From: Bj?rn T?pel <bjorn.topel@intel.com>
>>
>> Start using XSK_NAPI_WEIGHT as NAPI poll budget for the AF_XDP Rx
>> zero-copy path.
>
> Could you please add the description from the patch series cover letter
> to this commit too? To my knowledge, the message in the cover letter
> won?t be stored in the git repository.
>
Paul, thanks for the input! The netdev/bpf trees always include the
cover letter in the merge commit.
Cheers,
Bj?rn
>> Signed-off-by: Bj?rn T?pel <bjorn.topel@intel.com>
>> ---
>> ? drivers/net/ethernet/intel/ixgbe/ixgbe_xsk.c | 2 +-
>> ? 1 file changed, 1 insertion(+), 1 deletion(-)
>
> [?]
>
>
> Kind regards,
>
> Paul
next prev parent reply other threads:[~2020-09-08 11:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 15:02 [Intel-wired-lan] [PATCH bpf-next 0/4] xsk: increase NAPI budget for AF_XDP zero-copy path =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-09-07 15:02 ` [Intel-wired-lan] [PATCH bpf-next 1/4] xsk: add XSK_NAPI_WEIGHT define =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-09-07 15:02 ` [Intel-wired-lan] [PATCH bpf-next 2/4] i40e, xsk: use XSK_NAPI_WEIGHT as NAPI poll budget =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-09-07 15:02 ` [Intel-wired-lan] [PATCH bpf-next 3/4] ice, " =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-09-07 15:02 ` [Intel-wired-lan] [PATCH bpf-next 4/4] ixgbe, " =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-09-07 19:32 ` Jakub Kicinski
2020-09-08 5:38 ` =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-09-08 9:45 ` Eric Dumazet
2020-09-08 11:49 ` =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2020-09-08 15:12 ` Eric Dumazet
2020-09-08 10:12 ` Paul Menzel
2020-09-08 11:12 ` =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?= [this message]
2020-09-08 11:20 ` Paul Menzel
2020-09-08 11:43 ` =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
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=0fb03a39-d098-8fc9-ba70-e919ef8e091e@intel.com \
--to=bjorn.topel@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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