Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases > #352
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.readnews.com!news-xxxfer.readnews.com!webuse.net!not-for-mail |
|---|---|
| From | "daydreamer" <sundaresh.venugopal@gmail.com> |
| Newsgroups | comp.databases |
| Subject | Thread safe |
| Message-ID | <20130214035600392@webuse.net> (permalink) |
| Date | Thu, 14 Feb 2013 03:56:00 GMT |
| X-Newsreader | www.webuse.net |
| X-Complaints-To | abuse@webuse.net |
| NNTP-Posting-Host | 117.202.104.113 |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=ISO-8859-15 |
| Content-Transfer-Encoding | 8bit |
| Xref | csiph.com comp.databases:352 |
Show key headers only | View raw
I have a tree of recursive small hash tables. A small part of each hash table is stored in memory and the actual tables, in a file. This is for a simple experimental hash/trie based database organization.I wish to make this database thread safe. I intend to do so at the hash table level, to permit several threads to simultaneously read the hash table, but only one thread at a time to write or change the hash table. What is the best way to do accomplish this ? Also what happens if a thread holding a write lock on a hash table is abruptly terminated, never releasing that lock, for other threads to access the table ? Posted using www.webuse.net
Back to comp.databases | Previous | Next — Next in thread | Find similar | Unroll thread
Thread safe "daydreamer" <sundaresh.venugopal@gmail.com> - 2013-02-14 03:56 +0000
Re: Thread safe Kees Nuyt <k.nuyt@nospam.demon.nl> - 2013-02-14 22:33 +0100
Re: Thread safe "daydreamer" <sundaresh.venugopal@gmail.com> - 2013-02-15 04:07 +0000
csiph-web