Linux Perf Users
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	 Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	 Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	 Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	 linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH v3] perf bench: add --write-size option to sched pipe
Date: Mon, 1 Jun 2026 04:10:29 -0700	[thread overview]
Message-ID: <ah1nxw7jdbL69wvy@gmail.com> (raw)
In-Reply-To: <ahcqXqbjNlU-viPj@google.com>

Hello Namhyung,

On Wed, May 27, 2026 at 10:31:10AM -0700, Namhyung Kim wrote:
> On Wed, May 27, 2026 at 06:42:59AM -0700, Breno Leitao wrote:
> > +static inline int write_pipe(struct thread_data *td)
> > +{
> > +	unsigned int done = 0;
> > +	int ret;
> > +
> > +	while (done < write_size) {
> > +		ret = write(td->pipe_write, td->buf + done, write_size - done);
> > +		if (ret < 0) {
> > +			if (nonblocking && errno == EWOULDBLOCK)
> > +				continue;
> 
> Don't we also need the blocking part?

Just to make sure I'm reading this right: do you mean the writer
should epoll_wait() on EPOLLOUT before retrying (symmetric to what
read_pipe() does for EPOLLIN), so we sleep until the pipe drains
instead of spinning on EWOULDBLOCK? Or are you pointing at something
else — e.g. behavior in the blocking (!nonblocking) path?

> > +		if (ret == 0)
> >  			return ret;
> 
> Maybe it doesn't matter.. but shouldn't it return 'done' instead?

Ack!

> 
> > +		done += ret;
> >  	}
> > -	ret = read(td->pipe_read, &m, sizeof(int));
> > -	if (nonblocking && ret < 0 && errno == EWOULDBLOCK)
> > -		goto retry;
> > -	return ret;
> > +	return done;
> >  }
> >  
> >  static void *worker_thread(void *__tdata)
> >  {
> >  	struct thread_data *td = __tdata;
> > -	int i, ret, m = 0;
> > +	int i, ret;
> >  
> >  	ret = enter_cgroup(td->nr);
> >  	if (ret < 0) {
> > @@ -204,15 +241,38 @@ static void *worker_thread(void *__tdata)
> >  	}
> >  
> >  	for (i = 0; i < loops; i++) {
> > -		ret = write(td->pipe_write, &m, sizeof(int));
> > -		BUG_ON(ret != sizeof(int));
> > +		ret = write_pipe(td);
> > +		BUG_ON(ret < 0 || (unsigned int)ret != write_size);
> >  		ret = read_pipe(td);
> > -		BUG_ON(ret != sizeof(int));
> > +		BUG_ON(ret < 0 || (unsigned int)ret != write_size);
> 
> Nit: maybe comparing to the write_size is enough as it cannot be
> negative or bigger than INTMAX.

Ack, the following should be enough:

	BUG_ON(ret != (int)write_size);

Thanks for the review,
--breno

      reply	other threads:[~2026-06-01 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 13:42 [PATCH v3] perf bench: add --write-size option to sched pipe Breno Leitao
2026-05-27 14:07 ` sashiko-bot
2026-05-27 17:31 ` Namhyung Kim
2026-06-01 11:10   ` Breno Leitao [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=ah1nxw7jdbL69wvy@gmail.com \
    --to=leitao@debian.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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