From: Pavel Shilovsky <piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: mids and cifs sendrcv2
Date: Fri, 15 Apr 2011 22:41:37 +0400 [thread overview]
Message-ID: <BANLkTimQ-vgiTJVy5vcivwaqex2nCq9DLg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTiknBBtzjEjXK5N=SpUaU=b4GAos_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011/4/15 Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> I think nested mid structures (around a base of common mid fields)
> like the above is going to be the easiest way to handle the differences.
>
> I don't understand your PROTOCOL_ID #define though - we
> identify smb2 vs. cifs via a bool in the tcp server info struct,
> and presumably if we don't have access to the tcp server
> info struct we would have to add a field in the base mid
> (struct mid_q_entry) that indicates smb2 vs. cifs..
>
>
Good variant too. I don't it really matters how to get protocol
version - I just propose an idea how to organize structures.
--
Best regards,
Pavel Shilovsky.
next prev parent reply other threads:[~2011-04-15 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 16:39 mids and cifs sendrcv2 Steve French
[not found] ` <BANLkTi=tUrieqB4jCo0GRX3Np10JxJUP9Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-15 10:45 ` Pavel Shilovsky
[not found] ` <BANLkTikLfy=4BPESJEmOe+mBhKSRtC=W6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-15 13:38 ` Steve French
2011-04-15 15:21 ` Jeff Layton
[not found] ` <20110415112123.0a3c2996-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-04-22 10:26 ` Pavel Shilovsky
[not found] ` <BANLkTiknBBtzjEjXK5N=SpUaU=b4GAos_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-15 18:41 ` Pavel Shilovsky [this message]
2011-04-22 10:33 ` Pavel Shilovsky
2011-04-22 11:26 ` Jeff Layton
2011-04-22 11:45 ` Christoph Hellwig
[not found] ` <20110422114526.GA31546-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2011-04-26 19:40 ` Pavel Shilovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimQ-vgiTJVy5vcivwaqex2nCq9DLg@mail.gmail.com \
--to=piastryyy-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).