From: Eric Dumazet <eric.dumazet@gmail.com>
To: izabela.bakollari@gmail.com, nhorman@tuxdriver.com,
davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH net-next] dropwatch: Support monitoring of dropped frames
Date: Tue, 7 Jul 2020 10:36:14 -0700 [thread overview]
Message-ID: <48534d9d-49c3-5e43-d1f6-51b96ba7fd90@gmail.com> (raw)
In-Reply-To: <8aa6bcfe-8117-0fc9-1bc5-9b6a600e0972@gmail.com>
On 7/7/20 10:33 AM, Eric Dumazet wrote:
>
>
> What happens after this monitoring is started, then the admin does :
>
> rmmod ifb
>
I meant : rmmod dummy
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-07-07 17:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 17:15 [Linux-kernel-mentees] [PATCH net-next] dropwatch: Support monitoring of dropped frames izabela.bakollari
2020-07-07 17:33 ` Eric Dumazet
2020-07-07 17:36 ` Eric Dumazet [this message]
2020-07-07 17:52 ` Eric Dumazet
2020-07-08 13:54 ` Izabela Bakollari
2020-07-08 14:06 ` Izabela Bakollari
2020-07-07 21:00 ` kernel test robot
2020-07-08 0:27 ` kernel test robot
2020-08-04 16:09 ` [Linux-kernel-mentees] [PATCHv2 " izabela.bakollari
2020-08-04 21:28 ` Cong Wang
2020-08-04 21:58 ` Neil Horman
2020-08-04 23:14 ` David Miller
2020-08-05 10:44 ` Neil Horman
2020-08-10 13:39 ` Izabela Bakollari
2020-08-10 13:56 ` Greg KH
2020-08-31 13:18 ` Michal Schmidt
2020-09-02 16:05 ` Izabela Bakollari
2020-09-02 17:16 ` [Linux-kernel-mentees] [PATCHv3 " izabela.bakollari
2020-09-02 20:35 ` Eric Dumazet
2020-10-23 4:29 ` [Linux-kernel-mentees] [PATCHv4 " izabela.bakollari
2020-10-23 18:20 ` Jakub Kicinski
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=48534d9d-49c3-5e43-d1f6-51b96ba7fd90@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=izabela.bakollari@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).