Re: [PATCH] Searching for users of netncp and nwfs to help debug5.0problems

2002-11-26 Thread Julian Elischer


On Tue, 26 Nov 2002, Terry Lambert wrote:
 
 
 Uh, how exactly is that less obnoxious, given it's the same code
 with a different name and an obnoxious inline instead of a macro?
 8-).


it's shorter ..
 
 
  You can always get from a thread to a single process but the reverse
  always presents the question which thread?. This question can only be
  answered with external information or if you know there is only one
  thread at this moment.
 
 The answer is that the code doesn't care what thread; it would
 prefer to not have to think in terms of threads at all, but if
 you want to force it to, then it's going to think in terms of
 blocking contexts for the benefit of FreeBSD code it calls,
 and nothing else.

Hense the confusion as to whether to use a thread or a proc..
 
 Did you want me to update the patch to use your FIRST_THREAD_IN_PROC
 macro and resend it?


you could but the fact that FIRST_THREAD_IN_PROC() is used indicates
that the whole thing is broken anyway. Your edits are mostly mechanical
and don't actually solve the problem. To do that you probably need
to actually rewrite some of it I think.






To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: [PATCH] Searching for users of netncp and nwfs to help debug5.0problems

2002-11-26 Thread Terry Lambert
Julian Elischer wrote:
  The answer is that the code doesn't care what thread; it would
  prefer to not have to think in terms of threads at all, but if
  you want to force it to, then it's going to think in terms of
  blocking contexts for the benefit of FreeBSD code it calls,
  and nothing else.
 
 Hense the confusion as to whether to use a thread or a proc..

Not confusing at all.  The only issue is references to the
connection structure caches proc, which uses the first thread
on the cached proc; otherwise, it uses the thread that was
passed in.


  Did you want me to update the patch to use your FIRST_THREAD_IN_PROC
  macro and resend it?
 
 you could but the fact that FIRST_THREAD_IN_PROC() is used indicates
 that the whole thing is broken anyway. Your edits are mostly mechanical
 and don't actually solve the problem. To do that you probably need
 to actually rewrite some of it I think.

They were _intended_ to be mechanical edits.  It fixes the problem
for the people who were willing to fix it, but didn't have any
idea of how to do the edits.

I can't really rewrite the code for you, without risking that
Novell would claim that I did it with knowledge of the NUC
implementation... you _do_ remember the last time Novell and BSD
had an issue over code, right, back in 1994, after they bought
USL?

It's probably better that the patch I've done get to the people
who volunteered to fix the code, once it could be compiled, and
that the people who volunteered to help them with the threads
issues do so.  I've done as much as I can without legal risk.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Searching for users of netncp and nwfs to help debug5.0problems

2002-11-21 Thread Julian Elischer
As the person who broke it I'd like to help.. The problem was that it
referenced teh proc structure all over the place in several different
ways, and it was not obvious, without knowing the protocol which should
become thread references and which should stay proc references.

On Fri, 22 Nov 2002, Brad Knowles wrote:

 At 5:23 PM -0500 2002/11/21, Robert Watson wrote:
 
   (And, you have to bring your own test environment, as the second sentence
   suggests, but doesn't actually state).
 
   Over on -chat, we're in the process of putting together a list of 
 volunteers, hardware, organizational talent, etc... to help test out 
 -DP2.  Mark Murray is involved, but I personally would like to see at 
 least one or two more core team members committed to making this 
 happen.
 
   If we can get a suitable group of people together, with suitable 
 hardware, and get the coordination effort done correctly, I believe 
 that we can help make this a much more successful project.
 
 
   Your assistance in this effort would be greatly appreciated.
 
 -- 
 Brad Knowles, [EMAIL PROTECTED]
 
 They that can give up essential liberty to obtain a little temporary
 safety deserve neither liberty nor safety.
  -Benjamin Franklin, Historical Review of Pennsylvania.
 
 GCS/IT d+(-) s:+(++): a C++(+++)$ UMBSHI$ P+++ L+ !E W+++(--) N+ !w---
 O- M++ V PS++(+++) PE- Y+(++) PGP+++ t+(+++) 5++(+++) X++(+++) R+(+++)
 tv+(+++) b+() DI+() D+(++) G+() e++ h--- r---(+++)* z(+++)
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message