From: Jakub Kicinski <kuba@kernel.org>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net-next v5 06/12] net: homa: create homa_peer.h and homa_peer.c
Date: Tue, 7 Jan 2025 13:24:25 -0800 [thread overview]
Message-ID: <20250107132425.27a32652@kernel.org> (raw)
In-Reply-To: <CANn89iJKq=ArBwcKTGb0VcxexvA3d96hm39e75LJLvDhBaXiTw@mail.gmail.com>
On Tue, 7 Jan 2025 22:02:25 +0100 Eric Dumazet wrote:
> While you are at it, I suggest you test your patch with LOCKDEP enabled,
> and CONFIG_DEBUG_ATOMIC_SLEEP=y
>
> Using GFP_KERNEL while BH are blocked is not good.
In fact splice all of kernel/configs/debug.config into your
testing config.
next prev parent reply other threads:[~2025-01-07 21:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 18:12 [PATCH net-next v5 00/12] Begin upstreaming Homa transport protocol John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 01/12] net: homa: define user-visible API for Homa John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 02/12] net: homa: create homa_wire.h John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 03/12] net: homa: create shared Homa header files John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 04/12] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 05/12] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 06/12] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2025-01-07 14:15 ` Jakub Kicinski
2025-01-07 20:53 ` John Ousterhout
2025-01-07 21:02 ` Eric Dumazet
2025-01-07 21:24 ` Jakub Kicinski [this message]
2025-01-07 21:58 ` John Ousterhout
2025-01-08 0:02 ` Jakub Kicinski
2025-01-07 21:51 ` John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 07/12] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2025-01-08 14:56 ` D. Wythe
2025-01-09 18:35 ` John Ousterhout
2025-01-10 9:25 ` D. Wythe
2025-01-11 0:19 ` John Ousterhout
2025-01-11 8:30 ` Jason Xing
2025-01-13 17:11 ` John Ousterhout
2025-01-14 0:20 ` Jason Xing
2025-01-06 18:12 ` [PATCH net-next v5 08/12] net: homa: create homa_incoming.c John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 09/12] net: homa: create homa_outgoing.c John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 10/12] net: homa: create homa_timer.c John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 11/12] net: homa: create homa_plumbing.c homa_utils.c John Ousterhout
2025-01-06 18:12 ` [PATCH net-next v5 12/12] net: homa: create Makefile and Kconfig John Ousterhout
2025-01-13 17:27 ` [PATCH net-next v5 00/12] Begin upstreaming Homa transport protocol John Ousterhout
2025-01-13 20:06 ` Andrew Lunn
2025-01-13 20:47 ` John Ousterhout
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=20250107132425.27a32652@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
--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.