Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: [0/7] RFC: read DWARF psymtabs in the background
Date: Fri, 25 Jun 2010 21:36:00 -0000	[thread overview]
Message-ID: <20100625213606.GA30887@caradoc.them.org> (raw)
In-Reply-To: <m3eifu4ygd.fsf@fleche.redhat.com>

On Fri, Jun 25, 2010 at 03:03:14PM -0600, Tom Tromey wrote:
> >>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
> 
> Tom> I realize that threads are unpopular in many quarters, so this is an RFC.
> 
> Mark> Sorry, but this is pretty much a no-go for OpenBSD.  We have a
> Mark> userland threads implementation that puts file descriptors in
> Mark> non-blocking mode such that it can switch to another thread if I/O to
> Mark> that filedescriptor would block.  This has side effects if these file
> Mark> descriptors are shared with child processes :(.
> 
> If that is your only objection, it is no trouble to disable this code on
> a per-host basis.  All that is missing for that is some of the
> configury; all the code is designed to allow single-threaded operation.

FWIW, I think this is a reasonable thing to do.  I also think that
loading your future proposed indexes in the background would be a nice
feature.  For one thing, that lets us do them in parallel - great for
a task likely to be I/O dominated.  And on Windows hosts we already
use threads, so it'd win there too.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2010-06-25 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 18:22 Tom Tromey
2010-06-14 21:27 ` Michael Snyder
2010-06-15  3:00   ` Tom Tromey
2010-06-22 20:06 ` Mark Kettenis
2010-06-25 21:03   ` Tom Tromey
2010-06-25 21:36     ` Daniel Jacobowitz [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=20100625213606.GA30887@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=tromey@redhat.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