From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH v5 07/19] Create the BPF usdt_names and usdt_prids maps
Date: Sat, 12 Oct 2024 00:11:55 -0400 [thread overview]
Message-ID: <Zwn3C8AeutHoi7hz@oracle.com> (raw)
In-Reply-To: <890f24d7-aaa6-c957-97f4-e15954eed54e@oracle.com>
On Sat, Oct 12, 2024 at 12:04:59AM -0400, Eugene Loh wrote:
> On 10/11/24 19:53, Kris Van Hees wrote:
>
> > On Fri, Oct 11, 2024 at 06:56:16PM -0400, Eugene Loh via DTrace-devel wrote:
> > > On 10/10/24 00:55, Kris Van Hees wrote:
> > > > On Wed, Oct 09, 2024 at 01:45:34AM -0400, eugene.loh@oracle.com wrote:
> > > > > From: Eugene Loh <eugene.loh@oracle.com>
> > > > > + if (dtp->dt_usdt_namesmap_fd == -1)
> > > > > + return -1;
> > > > > +
> > > > > + dtp->dt_usdt_pridsmap_fd = create_gmap(dtp, "usdt_prids", BPF_MAP_TYPE_HASH,
> > > > > + dtp->dt_usdt_pridsmap_ksz, dtp->dt_usdt_pridsmap_vsz,
> > > > > + dtp->dt_options[DTRACEOPT_NUSDTPROBES]);
> > > > empty line perhaps?0~
> > > Sorry, I don't understand this comment.
> > Similar to the previous assignment followed by a conditional, I think that it
> > would make sense to insert an empty line between the assignment and the
> > conditional.
>
> Curious. It seemed to me to be very common for us to assign something and
> then immediately (no blank line) check its validity. Just a quick sanity
> check (not using this file, which at this point I've touched extensively), I
> tried libdtrace/dt_bpf.c. Indeed, lots of this practice, and you seemed to
> be the last person to touch those spots. I like the close spacing, but
> don't care a whole lot; I just wanted to double check since the patch seems
> to follow common practice in this particular regard.
Ah, oops, ignore me. That was a comment I originally wrote, then meant to
delete (note the odd characters following it in my original review email), but
clearly botched that. And then when you asked about it, I interpreted my
comment rather than actually looking back at what code it was really refering
to.
My mistake - please ignore. Sorry for the confusion.
prev parent reply other threads:[~2024-10-12 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 5:45 [PATCH v5 07/19] Create the BPF usdt_names and usdt_prids maps eugene.loh
2024-10-09 5:45 ` [PATCH v2 1/6] Deferred attach of underlying USDT probes eugene.loh
2024-10-16 15:58 ` Eugene Loh
2024-10-10 4:55 ` [PATCH v5 07/19] Create the BPF usdt_names and usdt_prids maps Kris Van Hees
2024-10-10 20:58 ` Kris Van Hees
2024-10-11 22:56 ` Eugene Loh
2024-10-11 23:53 ` [DTrace-devel] " Kris Van Hees
2024-10-12 4:04 ` Eugene Loh
2024-10-12 4:11 ` Kris Van Hees [this message]
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=Zwn3C8AeutHoi7hz@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.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.