On 09-Jul-2002 Julian Elischer wrote:
On Wed, 10 Jul 2002, Bruce Evans wrote:
Can these flags be changed asynchronously? If so, then everything needs
to be handled by ast() anyway. userret() should only check for work that
needs doing in the usual case, and hopefully there is none
On Wed, 10 Jul 2002, John Baldwin wrote:
On 09-Jul-2002 Julian Elischer wrote:
On Wed, 10 Jul 2002, Bruce Evans wrote:
Can these flags be changed asynchronously? If so, then everything needs
to be handled by ast() anyway. userret() should only check for work that
needs doing in the
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
It seems that really there is no one place that one can put code that will
be called ONCE and ONLY ONCE as a thread progresses to
]
To: FreeBSD current users [EMAIL PROTECTED]
Sent: Tuesday, July 09, 2002 2:40 PM
Subject: userret() , ast() and the end of syscalls
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast
On 09-Jul-2002 Julian Elischer wrote:
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
ast() is really a special form of a trap that is triggered by doing
a last-minute type check
On 09-Jul-2002 David Xu wrote:
I found the problem two weeks ago, but I can not find a better way to
avoid userret() to be called twice. so I keep silence. :(
It is only called twice if an AST is posted. It is _not_ always called
twice.
--
John Baldwin [EMAIL PROTECTED]
On 09-Jul-2002 John Baldwin wrote:
On 09-Jul-2002 Julian Elischer wrote:
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
ast() is really a special form of a trap that is
- Original Message -
From: John Baldwin [EMAIL PROTECTED]
To: John Baldwin [EMAIL PROTECTED]
Cc: FreeBSD current users [EMAIL PROTECTED]; FreeBSD current users
[EMAIL PROTECTED]; Julian Elischer [EMAIL PROTECTED]
Sent: Tuesday, July 09, 2002 8:40 PM
Subject: RE: userret() , ast
On Tue, 9 Jul 2002, John Baldwin wrote:
On 09-Jul-2002 John Baldwin wrote:
On 09-Jul-2002 Julian Elischer wrote:
A question to those who know..
why is userret() called both at the end of trap() or syscall()
and also almost immediatly again (often) at the end of ast().
ast() is
On Wed, 10 Jul 2002, Bruce Evans wrote:
Hopefully there won't be any unconditional code. Unconditional code
in userret() pessimizes all syscalls. Unconditional code added by KSEIII
pessimized basic syscall overhead by 10% according to lmbench2.
Mostly it's conditional..
if
On Wed, 10 Jul 2002, Bruce Evans wrote:
On Tue, 9 Jul 2002, Julian Elischer wrote:
On Wed, 10 Jul 2002, Bruce Evans wrote:
Hopefully there won't be any unconditional code. Unconditional code
in userret() pessimizes all syscalls. Unconditional code added by KSEIII
pessimized
On Wed, 10 Jul 2002, Bruce Evans wrote:
Can these flags be changed asynchronously? If so, then everything needs
to be handled by ast() anyway. userret() should only check for work that
needs doing in the usual case, and hopefully there is none (except for
things like ktrace).
That's an
12 matches
Mail list logo
