Re: CFR: Sequential mbuf read/write extensions

2001-02-12 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Boris Popo v writes: > No, in the current implementation mb_get* functions will work >properly. But mb_put* will fail. This can be avoided by implementing >alignment-safe set* macros (which can be written in two variants - first >form is for aligned objects an

Re: CFR: Sequential mbuf read/write extensions

2001-02-08 Thread Boris Popov
On Thu, 8 Feb 2001, Ian Dowse wrote: > It may be beneficial to use separate structs for the build and > breakdown operations. The two cases have slightly different > requirements: the mb_count field is only useful when building, and > mb_pos is only strictly necessary when breaking down mbuf chai

Re: CFR: Sequential mbuf read/write extensions

2001-02-08 Thread Ian Dowse
In message <[EMAIL PROTECTED]>, Boris Popo v writes: > Before starting import process for smbfs, I would like to >introduce new API which greatly simplifies process of packaging data into >mbufs and fetching it back (in fact, similar API already presented in the >tree, but it is private to t

Re: CFR: Sequential mbuf read/write extensions

2001-02-07 Thread Terry Lambert
> Before starting import process for smbfs, I would like to > introduce new API which greatly simplifies process of packaging data into > mbufs and fetching it back (in fact, similar API already presented in the > tree, but it is private to the netncp code and it will be really nice to > sha

Re: CFR: Sequential mbuf read/write extensions

2001-02-07 Thread Harti Brandt
On Wed, 7 Feb 2001, Boris Popov wrote: BP>> Using 'word' and 'doubleword' is rather confusing (when speeking of words BP>> I would think of 32 bit nowadays). BP> BP> Well, it depends. For me 'word', 'dword' and 'qword' are clear BP>from the good old 8bit days :) BP> BP> If numbers in the

Re: CFR: Sequential mbuf read/write extensions

2001-02-07 Thread Boris Popov
On Wed, 7 Feb 2001, Harti Brandt wrote: > But, I would recommend to stick with the ususal naming of size dependend > things, by appending a numeric suffix. Something like: > > int mb_get8(struct mbdata *mbp, u_int8_t *x); > int mb_get16(struct mbdata *mbp, u_int16_t *x); > int mb_get16le(stru

Re: CFR: Sequential mbuf read/write extensions

2001-02-07 Thread Harti Brandt
Looks nice, just what I needed two weeks ago and partly had to implement myself :-) But, I would recommend to stick with the ususal naming of size dependend things, by appending a numeric suffix. Something like: int mb_get8(struct mbdata *mbp, u_int8_t *x); int mb_get16(struct mbdata *mbp, u_

Re: CFR: Sequential mbuf read/write extensions

2001-02-06 Thread Boris Popov
On Tue, 6 Feb 2001, Alfred Perlstein wrote: > Looks really cool, I can't get to http://www.butya.kz/~bp/mbuf/, > but from the examples it looks very useful. Sorry, server was brought down and I wasn't notified :(. It should be ok now. > I was wondering if you planned or already had an A

Re: CFR: Sequential mbuf read/write extensions

2001-02-06 Thread Alfred Perlstein
* Boris Popov <[EMAIL PROTECTED]> [010206 03:51] wrote: > [Please trim CC list as necessary] > > Hello, > > Before starting import process for smbfs, I would like to > introduce new API which greatly simplifies process of packaging data into > mbufs and fetching it back (in fact, sim

CFR: Sequential mbuf read/write extensions

2001-02-06 Thread Boris Popov
[Please trim CC list as necessary] Hello, Before starting import process for smbfs, I would like to introduce new API which greatly simplifies process of packaging data into mbufs and fetching it back (in fact, similar API already presented in the tree, but it is private to the n