From: Jeff Dike <jdike@addtoit.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Syslets - Fix cachemiss_thread return value
Date: Thu, 31 May 2007 19:39:46 -0400 [thread overview]
Message-ID: <20070531233946.GA12493@c2.user-mode-linux.org> (raw)
In-Reply-To: <20070531220716.GL5488@mami.zabbo.net>
On Thu, May 31, 2007 at 03:07:16PM -0700, Zach Brown wrote:
> Can you explain what motivated you to send out this patch?
>
> It used to return 0. It was changed because, unlike the syslet
> syscalls, sys_io_submit() doesn't have a simple 0 value to indicate
> success. The current implementation wants to return the number of iocbs
> that were processed, including the one which blocked, from the cachemiss
> thread. So before calling into an operation it sets task_ret_ret() so
> that the cachemiss thread can return it if it takes over.
> task_ret_reg() is holding a return value that is being returned by the
> cachemiss thread on behalf of a sys_io_submit() which blocked.
>
> When I made the change I didn't really audit its effect on the other
> paths. I suppose it's time to do that, and you could help by telling me
> if you saw something bad happen :).
The bad thing was sys_async_exec returning -NOSYS every time a new
cachemiss thread was created.
Without this patch, you'll see sys_async_exec failures with either of
the demos I sent out. Dunno about the existing ones, but I bet they do
the same.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2007-05-31 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 18:19 [PATCH] Syslets - Fix cachemiss_thread return value Jeff Dike
2007-05-31 20:09 ` Ingo Molnar
2007-05-31 22:07 ` Zach Brown
2007-05-31 23:39 ` Jeff Dike [this message]
2007-06-01 0:00 ` Zach Brown
2007-06-07 23:27 ` Zach Brown
2007-06-08 16:10 ` Jeff Dike
2007-06-08 16:26 ` Zach Brown
2007-06-08 16:33 ` Jeff Dike
2007-06-08 16:46 ` Zach Brown
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=20070531233946.GA12493@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=zach.brown@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox