similar to: Design: Asynchronous I/O for single/multi-dbox

On Jun 13, 2011, at 10:30 AM, Jakob Stoklund Olesen wrote: > On Jun 13, 2011, at 12:29 AM, John McCall wrote: >> Let me make an analogy. We live in Germany. Sohail wants to drive to Spain. Duncan told him to go through France. You and Cameron are saying that the traffic in France is awful, and some friends who went to Italy didn't go through France. I am trying to point out that

On Jun 12, 2011, at 5:31 PM, Sohail Somani wrote: > On 11-06-12 7:40 PM, John McCall wrote: >> On Jun 12, 2011, at 2:14 PM, Cameron Zwarich wrote: >> >>>> On Jun 12, 2011, at 1:25 AM, Duncan Sands wrote: >>>> >>>>>> Hi Sohail, >>>>>> >>>>>>>> Is LLVM expressive enough to represent asynchronous

On Jun 13, 2011, at 12:29 AM, John McCall wrote: > Let me make an analogy. We live in Germany. Sohail wants to drive to Spain. Duncan told him to go through France. You and Cameron are saying that the traffic in France is awful, and some friends who went to Italy didn't go through France. I am trying to point out that Italy is not Spain, even though they are both on the Mediterranean,

 Hi, list,     I recently begin to study samba source code. Now I have some questions to ask. Can you give me some help?     The first question is what the relationship between samba versions(such as 3.x.x , 4.x.x) and samba3/samba4. In samba source code, I find two directories, souce3 and soure4. Do they mean  samba3 and samba4?  Actually, almost all docs in samba are about samba3, where to find

On 11-06-12 7:40 PM, John McCall wrote: > On Jun 12, 2011, at 2:14 PM, Cameron Zwarich wrote: > >> > On Jun 12, 2011, at 1:25 AM, Duncan Sands wrote: >> > >>> >> Hi Sohail, >>> >> >>>> >>> Is LLVM expressive enough to represent asynchronous exceptions? >>> >> >>> >> not currently. The

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1345046301 -3600 # Node ID 7cec0543f67cefe3755bbad0c2262fa2e820d746 # Parent 30bf79cc14d932fbe6ff572d0438e5a432f69b0a libxl: make domain resume API asynchronous Although the current implementation has no asynchromous parts I can envisage it needing to do bits of create/destroy like functionality which may need async

----- Forwarded message ----- Date: Sat, 18 Feb 2017 22:21:19 -0500 Subject: nbdkit async Hello, Hope this is the right person to contact regarding nbdkit design. I have a high latency massively parallel device that I am currently implementing as an nbdkit plugin in c++ and have run into some design limitations due to the synchronous callback interface nbdkit requires. Nbdkit is currently

I''m a bit unclear how to use/try de-duplication in asynchronous mode? Can someone kindly clarify? Is it as simple as enabling then disabling after something completes? Thanks -- This message posted from opensolaris.org

Hi, We've been using a modified nbdkit (ours is cbdkit internally) for about half a year now and since you guys appear to be working on a next version of the API I wanted to go over some of the limitations we hit with nbdkit that we think others may also hit for consideration into the batch of changes you are making to the api. About Us: Our primary use for nbdkit is to facilitate a disk

Hi everyone, This patchset is the latest approach I''m using for the Ceph storage daemon to keep track of which data has safely committed to disk. The basic idea is to not use the (problematic) user transaction ioctls at all. Instead, the daemon quiesces its own write requests, initiates an async snapshot, and then continues. The snapshot approach is nice because it provides rollback.

On 11-06-12 8:53 PM, John McCall wrote: >> > The CFG point is a valid point. In what I've read on the topic so far >> > (yay Internet), it seems like the CFG would have to represent the fact >> > that control can jump to a handler after nearly every instruction in the >> > presence of async exceptions. The Hotspot compiler probably does this. >> >

On Jun 12, 2011, at 5:53 PM, John McCall wrote: > > On Jun 12, 2011, at 5:31 PM, Sohail Somani wrote: > >> On 11-06-12 7:40 PM, John McCall wrote: >>> On Jun 12, 2011, at 2:14 PM, Cameron Zwarich wrote: >>> >>>>> On Jun 12, 2011, at 1:25 AM, Duncan Sands wrote: >>>>> >>>>>>> Hi Sohail,

> > On 03 Feb 2019, at 22:07, MRob <mrobti at insiberia.net> wrote: > > Hi, I originally picked mdbox because I had the impression from reading about it on the mailing list that it was more performant and that it would conserve disc space. > > But lately i found mailboxes have nearly double the storage as reported. I mean, IMAP QUOTA reports around 900MB for one account

This is about how to implement multiple msgs/file dbox format. The current v1.1's one msg/file design would stay pretty much the same and it would be compatible with this new design. dbox directories with multiple msgs/file would be like: ~/dbox/storage/ has the actual mail data for all mailboxes ~/dbox/mailboxes/ has subdirectories containing mailboxes and their indexes Also since dbox

On Jun 13, 2011, at 10:50 AM, John McCall wrote: > On Jun 13, 2011, at 10:30 AM, Jakob Stoklund Olesen wrote: >> The try block would look something like: >> >> call _malloc >> movq %rax, p(%rpb) >> >> If you take an exception between those two instructions, you are leaking memory. > > This is primarily an argument that C is not a good language to

On Thu, Apr 11, 2019 at 9:02 AM Pankaj Gupta <pagupta at redhat.com> wrote: > > > > > > > > > This patch adds functionality to perform flush from guest > > > to host over VIRTIO. We are registering a callback based > > > on 'nd_region' type. virtio_pmem driver requires this special > > > flush function. For rest of the region

On Tue, Apr 9, 2019 at 9:09 PM Pankaj Gupta <pagupta at redhat.com> wrote: > > This patch adds functionality to perform flush from guest > to host over VIRTIO. We are registering a callback based > on 'nd_region' type. virtio_pmem driver requires this special > flush function. For rest of the region types we are registering > existing flush function. Report error

On Tue, Apr 9, 2019 at 9:09 PM Pankaj Gupta <pagupta at redhat.com> wrote: > > This patch adds functionality to perform flush from guest > to host over VIRTIO. We are registering a callback based > on 'nd_region' type. virtio_pmem driver requires this special > flush function. For rest of the region types we are registering > existing flush function. Report error

On Jun 12, 2011, at 11:24 PM, Bill Wendling wrote: > On Jun 12, 2011, at 4:40 PM, John McCall wrote: > >> On Jun 12, 2011, at 2:14 PM, Cameron Zwarich wrote: >> >>> On Jun 12, 2011, at 1:25 AM, Duncan Sands wrote: >>> >>>> Hi Sohail, >>>> >>>>> Is LLVM expressive enough to represent asynchronous exceptions?

On 2011-06-12, at 4:40 PM, John McCall wrote: > On Jun 12, 2011, at 2:14 PM, Cameron Zwarich wrote: > >> On Jun 12, 2011, at 1:25 AM, Duncan Sands wrote: >> >>> Hi Sohail, >>> >>>> Is LLVM expressive enough to represent asynchronous exceptions? >>> >>> not currently. The first step in this direction is to get rid of the invoke