From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Alexander Aring <aahringo@redhat.com>, linux-trace-devel@vger.kernel.org
Cc: linux-trace-users@vger.kernel.org
Subject: Re: RFC: using NIC DMA ring as tracing buffer?
Date: Tue, 16 Apr 2024 10:48:57 -0400 [thread overview]
Message-ID: <46859f90-bdf6-4502-bf6a-4add6dad3668@efficios.com> (raw)
In-Reply-To: <CAK-6q+iAuLM35C1kZbDpS4E_61vC9A1mTpJb+nzhfX5DPUQkGg@mail.gmail.com>
On 2024-04-16 10:41, Alexander Aring wrote:
> Hi all,
>
> I have an idea about using the DMA rings of a networking card as a
> tracing buffer.
The first thing I'd be worried about is overhead caused by
false-sharing if you trace a large SMP/many-core system all
into the same global NIC buffer. The cache lines will bounce
left and right which is bad performance-wise.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2024-04-16 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 14:41 RFC: using NIC DMA ring as tracing buffer? Alexander Aring
2024-04-16 14:48 ` Mathieu Desnoyers [this message]
2024-04-17 22:51 ` Alexander Aring
2024-04-17 23:05 ` Alexander Aring
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=46859f90-bdf6-4502-bf6a-4add6dad3668@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=aahringo@redhat.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).