On Wed, 8 May 2002 09:16:56 -0700,
Alfred Perlstein <[EMAIL PROTECTED]> said:
bright> * Seigo Tanimura <[EMAIL PROTECTED]> [020508 04:59] wrote:
>>
>> I would like to commit this patch in one or two weeks to start working
>> on a possible race between a user process and a netisr kthread,
>> pr
On Sun, 28 Apr 2002, Seigo Tanimura wrote:
> On Wed, 24 Apr 2002 20:08:56 +0900,
> Seigo Tanimura <[EMAIL PROTECTED]> said:
>
> Seigo> I am now working on locking down a socket. (I have heard that Jeffrey
> Seigo> Hsu is also doing that, but I have never seen his patch. Has anyone
> Seigo> se
On Thu, 25 Apr 2002 11:04:32 -0700 (PDT),
[EMAIL PROTECTED] (Jeffrey Hsu) said:
hsu> If you compare the two approaches, the BSD/OS approach is simpler
hsu> because it is coarse. You're confusing finer grain locking with
hsu> better.
Well, maybe my patch just seems more fine-grained than BSD/O
On Wed, 24 Apr 2002 20:08:56 +0900,
Seigo Tanimura <[EMAIL PROTECTED]> said:
Seigo> I am now working on locking down a socket. (I have heard that Jeffrey
Seigo> Hsu is also doing that, but I have never seen his patch. Has anyone
Seigo> seen that?) My first milestone patch is now available at:
In article <[EMAIL PROTECTED]> you write:
>I am now working on locking down a socket. (I have heard that Jeffrey
>Hsu is also doing that, but I have never seen his patch. Has anyone
>seen that?)
I have. :-) I do coarse-grain locking at the inpcb and sockbuf level as
is done in BSD/OS. This is
If you compare the two approaches, the BSD/OS approach is simpler
because it is coarse. You're confusing finer grain locking with
better.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
* Jeffrey Hsu <[EMAIL PROTECTED]> [020425 10:50] wrote:
> In article <[EMAIL PROTECTED]> you write:
> >I am now working on locking down a socket. (I have heard that Jeffrey
> >Hsu is also doing that, but I have never seen his patch. Has anyone
> >seen that?)
>
> I have. :-) I do coarse-grain l
On Thu, 25 Apr 2002 18:01:51 +0900,
Seigo Tanimura <[EMAIL PROTECTED]> said:
Seigo> On Thu, 25 Apr 2002 01:36:44 -0700,
Seigo> Alfred Perlstein <[EMAIL PROTECTED]> said:
bright> * Seigo Tanimura <[EMAIL PROTECTED]> [020425 01:19] wrote:
>>> >>
>>> >> http://people.FreeBSD.org/~tanimura/patc
On Thu, 25 Apr 2002 01:36:44 -0700,
Alfred Perlstein <[EMAIL PROTECTED]> said:
bright> * Seigo Tanimura <[EMAIL PROTECTED]> [020425 01:19] wrote:
>> >>
>> >> http://people.FreeBSD.org/~tanimura/patches/socket_milestone1.diff.gz
>> >>
bright> Why is there a "sigio" lock in this delta?
I shou
* Seigo Tanimura <[EMAIL PROTECTED]> [020425 01:19] wrote:
> >>
> >> http://people.FreeBSD.org/~tanimura/patches/socket_milestone1.diff.gz
> >>
This looks really good so far!
Needs some more comments explaining socq_lock.
Watch long line wraps.
Why is there a "sigio" lock in this delta?
--
On Wed, 24 Apr 2002 10:18:01 -0400 (EDT),
John Baldwin <[EMAIL PROTECTED]> said:
jhb> On 24-Apr-2002 Seigo Tanimura wrote:
>> I am now working on locking down a socket. (I have heard that Jeffrey
>> Hsu is also doing that, but I have never seen his patch. Has anyone
>> seen that?) My first mi
On Wed, 24 Apr 2002 08:57:41 -0400,
Bosko Milekic <[EMAIL PROTECTED]> said:
bmilekic> I've literally just had time to glance at this so far, but can you, if
bmilekic> you don't mind, please just briefly explain what BSD/OS does with
bmilekic> sockbuf locking (do they use the same lock, or...?)
On 24-Apr-2002 Seigo Tanimura wrote:
> I am now working on locking down a socket. (I have heard that Jeffrey
> Hsu is also doing that, but I have never seen his patch. Has anyone
> seen that?) My first milestone patch is now available at:
>
>
> http://people.FreeBSD.org/~tanimura/patches/sock
13 matches
Mail list logo
