Network api documentation.

[Jeremy Allison]

On Fri, Aug 30, 2013 at 11:16:01AM +0800, Marcelo Araujo wrote:
> 
> 2. RSS:
> I have some 10G Intel interfaces that support RSS, I set the RSS bit and
> set also 2 queues on server side. The client behavior in this case is
> different, the client send a second write command, however the first write
> command was not finished yet and it can be a big problem in currently samba
> architecture. As I saw, I can't write the data from a not continuous offset.

Not true. Every write command contains an offset. We handle non-continuous
writes all the time.

> 4. With the RSS, the client send the second write, but I fail to catch it
> on server side, because samba architecture does support only continuous
> offset for the write command in my understanding.

I think this understanding is incorrect :-).

> I'm thinking how to deal with this not continuous offset on the write
> command, and I would like to have some suggestions.
> 
> Maybe write a set that will individually take care of the write command,
> that would be outside of smbd, the smbd would pass the write offset to this
> new thread or process, this new thread/process will have such like a queue
> where it will organize the write in a continuous offset. This new
> thread/process would handle all write commands from any smbd thread that
> has smb3 multichannel negotiated.

Take a look at the aio pthread code. I think this does
what you want.

Jeremy.