[Nbd] Book Your Home at Pre-Launch Prices Now!!

-- Transform Data into Opportunity. Accelerate data analysis in your application

[Nbd] [PATCH v3 1/5] doc: Minor consistency issues

- Fix a typo - consistently use trailing spacing at the end of layout descriptions - drop other unneeded trailing spacing - add a missing sentence for consistency on what a client should do with unknown flags - fix a terminology change missed in a prior patch Signed-off-by: Eric Blake --- doc/pr

[Nbd] [PATCH v3 0/5] Structured replies

since v2: more wording tweaks based on review comments, split out some independent cleanups that were observed during review, re-add NBD_FLAG_SEND_DF for ease of user/kernel split in client, allow NBD_REPLY_TYPE_NONE even after an error, more consistent use of the term 'chunk' to mean a message wi

[Nbd] Pay only 20% now & no pre-EMIs till possession to book your home at Godrej Prana, Undri in Pune

[Nbd] [PATCH v3 3/5] doc: Reformat description of Transmission phase

Rearrange a paragraph and add some headings, so that the next patch adding a Structured Reply has less churn. Signed-off-by: Eric Blake --- doc/proto.md | 29 ++--- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/doc/proto.md b/doc/proto.md index 04d4a13..

[Nbd] [PATCH v3 5/5] RFC: doc: Promote structured reply out of experimental

Should not be applied until we have a working implementation, in case we need to tweak things. Demonstrates the amount of word-smithing required to promote structured replies to non-experimental. In many cases, I was able to preserve entire paragraphs (but sometimes reflowed at different indentat

[Nbd] [PATCH v3 2/5] doc: Clean up wording on UTF-8 and REP_SERVER usage

Consistently use the spelling UTF-8. Make it clear that when a UTF-8 string is transmitted, the sender need not transmit a terminating NUL byte, so the receiver must pay attention to length. Require error messages to be UTF-8 (thankfully, this would include the case of an all-ASCII LC_ALL=C strer

[Nbd] [PATCH v3 4/5] doc: Propose STRUCTURED_REPLY extension

The existing transmission phase protocol is difficult to sniff, because correct interpretation of the server stream requires context from the client stream (or risks false positives if data payloads happen to contain the protocol magic numbers). It also prohibits the ability to do efficient sparse

[Nbd] Your health check-up package is ready

Save upto Rs.3945/- on special health check-up packages Click here to avail this offer

Re: [Nbd] [Qemu-devel] [PATCH v2 3/3] doc: Propose Structured Read extension

On 03/30/2016 01:51 PM, Wouter Verhelst wrote: >> >> I'm a bit reluctant to put ordering requirements on option haggling >> (that option A must be turned on before option B), > > Yes, me too. > >> but then again, the >> SELECT extension requires NBD_OPT_SELECT to be haggled prior to >> NBD_OPT_GO

[Nbd] Mahindra Mojo, now in your city!

-- Transform Data into Opportunity. Accelerate data analysis in your application

[Nbd] No Annual fee or joining fee on your Platinum Rewards Credit Card.

Dripcore has sent you this email since you have permitted Dripcore to send you promotional communication/ offers. Standard Chartered Bank does not have access to this database, hence even if you are unsubscribed to Standard Chartered Bank communication, you may still receive offers from Dripcore.

Re: [Nbd] [Qemu-devel] [PATCH v2 3/3] doc: Propose Structured Read extension

Eric, >>> However, for ease of implementation, a >>> +server MAY close the connection rather than entering transmission >>> +phase if, at the end of option haggling, the client has negotiated >>> +another command that requires a structured reply but did not also >>> +negotiate Stru

Re: [Nbd] This list and spam

On Wed, Mar 30, 2016 at 09:38:28AM +0200, Wouter Verhelst wrote: > I'm going to contact sourceforge support one time to see if there's > something they can or plan to do. If that doesn't result in a > satisfactory resolution, I'll go and see if I can find something better.

Re: [Nbd] [PATCH v2 3/3] doc: Propose Structured Read extension

On Wed, Mar 30, 2016 at 03:16:02PM -0600, Eric Blake wrote: > On 03/30/2016 02:44 PM, Wouter Verhelst wrote: > >> > >> @@ -579,7 +602,7 @@ To remedy this, a `SELECT` extension is envisioned. > >> This extension adds > >> two option requests and one error reply type, and extends one existing > >>

Re: [Nbd] [Qemu-devel] [PATCH v2 3/3] doc: Propose Structured Read extension

On Wed, Mar 30, 2016 at 02:54:41PM -0600, Eric Blake wrote: > On 03/30/2016 01:51 PM, Wouter Verhelst wrote: > > > (side note: this seems to be mostly an NBD discussion at this point. > > Does qemu-devel need to be in the loop before we've finished that? I > > don't care either way, but then I don

Re: [Nbd] [PATCH v2 3/3] doc: Propose Structured Read extension

On 03/30/2016 02:44 PM, Wouter Verhelst wrote: >> >> @@ -579,7 +602,7 @@ To remedy this, a `SELECT` extension is envisioned. This >> extension adds >> two option requests and one error reply type, and extends one existing >> option reply type. >> >> -* `NBD_OPT_SELECT` >> +* `NBD_OPT_SELECT` (6)

Re: [Nbd] [Qemu-devel] [PATCH v2 3/3] doc: Propose Structured Read extension

On 03/30/2016 01:51 PM, Wouter Verhelst wrote: > (side note: this seems to be mostly an NBD discussion at this point. > Does qemu-devel need to be in the loop before we've finished that? I > don't care either way, but then I don't want to bore or annoy people...) Well, it stemmed out of qemu's de

Re: [Nbd] [PATCH v2 3/3] doc: Propose Structured Read extension

So, On Tue, Mar 29, 2016 at 05:01:00PM -0600, Eric Blake wrote: [...] > +- `NBD_OPT_STRUCTURED_READ` (8) > + > +Defined by the experimental `Structured Read` extension; see below. (detail: that makes the "structured read" extension be typographically different from everything else. Either mak

Re: [Nbd] [PATCHv2] Strawman proposal for NBD structured replies

On Wed, Mar 30, 2016 at 12:43:57PM -0600, Eric Blake wrote: > On 03/30/2016 01:33 AM, Wouter Verhelst wrote: > > Morning, > > > > On Wed, Mar 30, 2016 at 07:59:15AM +0100, Alex Bligh wrote: > >> On 30 Mar 2016, at 00:17, Eric Blake wrote: > > -The server replies with: > +Replies ta

Re: [Nbd] [Qemu-devel] [PATCH v2 3/3] doc: Propose Structured Read extension

Hi all, (side note: this seems to be mostly an NBD discussion at this point. Does qemu-devel need to be in the loop before we've finished that? I don't care either way, but then I don't want to bore or annoy people...) On Wed, Mar 30, 2016 at 11:45:04AM -0600, Eric Blake wrote: > On 03/30/2016 12

[Nbd] NBD_REP_SERVER layout [was: [Qemu-devel] [PATCHv2] Strawman proposal for NBD structured replies]

On 03/30/2016 12:43 PM, Eric Blake wrote: > On that tangent, I found SELECT slightly ambiguous (particularly since > I'm also considering a proposal to modify NBD_REP_SERVER to expose > alignment details, so it would have to play nicely with SELECT): > > Based on normative text alone, we would ha

Re: [Nbd] [PATCHv2] Strawman proposal for NBD structured replies

On 03/30/2016 01:33 AM, Wouter Verhelst wrote: > Morning, > > On Wed, Mar 30, 2016 at 07:59:15AM +0100, Alex Bligh wrote: >> On 30 Mar 2016, at 00:17, Eric Blake wrote: -The server replies with: +Replies take one of two forms. They may either be structured replies, >>> >>> Hmm, you

Re: [Nbd] [Qemu-devel] [PATCH v2 3/3] doc: Propose Structured Read extension

On 03/30/2016 12:50 AM, Alex Bligh wrote: > Eric, > > There's a lot in common between our two proposals now (unsurprisingly). > You've highlighted the differences in the other mail and I'll > comment on them there. You may want to steal some of my wording as > I think there are bits I've got that

[Nbd] VVIP Homes: Pay Just 5% to Book, No EMI Till Possession, Upto 100% Cashback Too

To UNSUBSCRIBE click here. -- Transform Data into Opportunity. Accelerate data

Re: [Nbd] [PATCH v2 0/3] NBD Structured Read

Hi Eric, On Tue, Mar 29, 2016 at 05:00:57PM -0600, Eric Blake wrote: > I wrote this in parallel with Alex's strawman proposals, so I > may have picked up on some of his ideas, while diverging in > other places. > > Changes since v1: rebase, resend some pre-req patches, switch > from global/client

Re: [Nbd] This list and spam

On Wed, Mar 30, 2016 at 08:02:05AM +0100, Alex Bligh wrote: > I get more spam to this list than messages (by an order of 10). Yeah, it's pretty horrible. The mail archives are a mess, too. This is mainly because their interface for marking mails in the archives as spam is possibly even worse than

Re: [Nbd] [PATCHv2] Strawman proposal for NBD structured replies

Morning, On Wed, Mar 30, 2016 at 07:59:15AM +0100, Alex Bligh wrote: > On 30 Mar 2016, at 00:17, Eric Blake wrote: > >> > >> -The server replies with: > >> +Replies take one of two forms. They may either be structured replies, > > > > Hmm, you put your strawman directly in the 'transmission pha

[Nbd] This list and spam

I get more spam to this list than messages (by an order of 10). That means my spam detectors (and I've just changed, and the new service does the same) think lots of genuine email is spam. What's the chance of moving to google groups or similar? This permits email subscription (digest or individua

Re: [Nbd] [PATCHv2] Strawman proposal for NBD structured replies

On 30 Mar 2016, at 00:17, Eric Blake wrote: >> >> -The server replies with: >> +Replies take one of two forms. They may either be structured replies, > > Hmm, you put your strawman directly in the 'transmission phase' section, > while mine is deferred to the 'Experimental Extensions' section, a