linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shahab Vahedi <Shahab.Vahedi@synopsys.com>
To: bpf <bpf@vger.kernel.org>
Cc: "linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	"Björn Töpel" <bjorn@kernel.org>,
	"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
	"Shahab Vahedi" <list+bpf@vahedi.org>,
	"Shahab Vahedi" <Shahab.Vahedi@synopsys.com>,
	"Vineet Gupta" <vgupta@kernel.org>
Subject: Re: [PATCH bpf-next v1] ARC: Add eBPF JIT support
Date: Mon, 26 Feb 2024 18:39:17 +0000	[thread overview]
Message-ID: <ccba43ce-89f0-43f1-a40f-c6fdd33ee256@synopsys.com> (raw)
In-Reply-To: <520bb8de-3515-47a6-b9e1-ede9d26b4658@synopsys.com>

Hello list,

I know this is not a small patch, but could someone skim over it?
If there's anything that I can do to make the review process easier,
please let me know.

I already intend to change the "commit message" in the following ways:

- Fix a typo: interpretor -> interpreter
- Mentioning the version of BPF CPU support: cpu=v4 (the latest)
- Saying a little bit about the performance improvement: 2-10 fold


Thank you in advance,
Shahab
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

  reply	other threads:[~2024-02-26 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 13:19 [PATCH bpf-next v1] ARC: Add eBPF JIT support Shahab Vahedi
2024-02-14  2:39 ` Alexei Starovoitov
2024-02-14  5:53   ` Vineet Gupta
2024-02-14 14:54   ` Shahab Vahedi
2024-02-26 18:39     ` Shahab Vahedi [this message]
2024-03-03 17:18 ` Björn Töpel
2024-03-05 15:22   ` Shahab Vahedi
2024-03-06 16:21     ` Björn Töpel
2024-04-30 15:01     ` Shahab Vahedi

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=ccba43ce-89f0-43f1-a40f-c6fdd33ee256@synopsys.com \
    --to=shahab.vahedi@synopsys.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=list+bpf@vahedi.org \
    --cc=vgupta@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).