9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: quanstro <quanstro@gmail.com>
To: plan9port-dev@googlegroups.com
Cc: quanstro@gmail.com,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: acme, upas commits
Date: Tue, 13 May 2014 06:58:06 -0700	[thread overview]
Message-ID: <4e562e73-7f55-48f1-a388-1b73d84078ed@googlegroups.com> (raw)
In-Reply-To: <CAPavXpCjQ1+3pwWDTxrQJ_y5EgTMhbPxS6kEAk9=ES02jhNfsA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3500 bytes --]

right.  as i mentioned, the structure of acme had been to keep all the
threads that might otherwise need locking in the same proc so as to
use cooperative multitasking to avoid the need for explicit locking.
therefore, i would not expect this bug to happen unless this code is
either somehow exceptional, or acme was working in to procs when it
should not be, or perhaps threads are not as cooperative as they might
be.

without resolution on this issue, it would seem likely that other bugs
are lurking.  even if they have not yet been found.  that is, it might be
that a more systemic fix may be necessary.

- erik

On Tuesday, May 13, 2014 9:34:17 AM UTC-4, Alexander Sychev wrote:
>
> Are there other similar bugs?
>
> Actually, I was digging only the amail's problem.
> Now I can't recall all details (it was few months ago), but I had saw
> parallel calls of regexp functions without any lock and I thought it should
> be such way.
>
>
> On Tue, May 13, 2014 at 4:44 PM, quanstro <quan...@gmail.com <javascript:>
> > wrote:
>
>> did you track down why the unexpected concurrency was happening?  this
>> could result in other bugs as well.
>>
>> - erik
>>
>>
>> On Tuesday, May 13, 2014 8:34:29 AM UTC-4, Alexander Sychev wrote:
>>
>>> There were problems in p9p under linux, when amail makes  simultaneous
>>> searches in different windows.
>>>
>>>
>>> On Tue, May 13, 2014 at 4:23 PM, quanstro <quan...@gmail.com> wrote:
>>>
>>>> in theory the threads that interact with regular expressions in acme
>>>> are all cooperatively scheduled.  have you seen a case where they
>>>> are not?  did pthreads blow up the model?
>>>>
>>>> - erik
>>>>
>>>>
>>>> On Tuesday, May 13, 2014 7:11:02 AM UTC-4, Alexander Sychev wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have commited some changes in my experimental fork of plan9port.
>>>>> https://bitbucket.org/santucco/plan9port
>>>>>
>>>>> For acme I made thread safe processing of regular expressions
>>>>> (actually by creating some context).
>>>>> For upas/nfs I made a monitoring of all mailboxes and a decoding of
>>>>> international names of mailboxes.
>>>>>
>>>>> I'm living with these changes for some time, they are working.
>>>>>
>>>>> P.S.
>>>>> By the way, new log feature is excellent, it's a time to make more
>>>>> applications for acme :-)
>>>>> --
>>>>> Best regards,
>>>>>   santucco
>>>>>
>>>>  --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "plan9port-dev" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to plan9port-de...@googlegroups.com.
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>>   santucco
>>>
>>  --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "plan9port-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to plan9port-de...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Best regards,
>   santucco
>

--

---
You received this message because you are subscribed to the Google Groups "plan9port-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plan9port-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 6300 bytes --]

      reply	other threads:[~2014-05-13 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 11:11 Alexander Sychev
2014-05-13 12:23 ` quanstro
2014-05-13 12:34   ` Alexander Sychev
2014-05-13 12:44     ` quanstro
2014-05-13 13:34       ` Alexander Sychev
2014-05-13 13:58         ` quanstro [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=4e562e73-7f55-48f1-a388-1b73d84078ed@googlegroups.com \
    --to=quanstro@gmail.com \
    --cc=9fans@9fans.net \
    --cc=plan9port-dev@googlegroups.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;
as well as URLs for NNTP newsgroup(s).