From: Jeremy Allison <jra@samba.org>
To: Tom Talpey <ttalpey@microsoft.com>
Cc: "Aurélien Aptel" <aaptel@suse.com>,
"Steve French" <smfrench@gmail.com>,
"Theodore Tso" <tytso@mit.edu>,
"Matthew Wilcox" <willy@infradead.org>,
"ebiggers@kernel.org" <ebiggers@kernel.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Streams support in Linux
Date: Wed, 29 Aug 2018 09:00:09 -0700 [thread overview]
Message-ID: <20180829160009.GB114671@jra3> (raw)
In-Reply-To: <BL0PR2101MB0993988DE5B4A5B5367B124DA0090@BL0PR2101MB0993.namprd21.prod.outlook.com>
On Wed, Aug 29, 2018 at 03:02:01PM +0000, Tom Talpey wrote:
> > -----Original Message-----
> > From: Aur�lien Aptel <aaptel@suse.com>
> > Sent: Wednesday, August 29, 2018 9:55 AM
> > To: Tom Talpey <ttalpey@microsoft.com>; Jeremy Allison <jra@samba.org>;
> > Steve French <smfrench@gmail.com>
> > Cc: Theodore Tso <tytso@mit.edu>; Matthew Wilcox <willy@infradead.org>;
> > ebiggers@kernel.org; Al Viro <viro@zeniv.linux.org.uk>; linux-fsdevel <linux-
> > fsdevel@vger.kernel.org>
> > Subject: RE: Streams support in Linux
> >
> > Tom Talpey <ttalpey@microsoft.com> writes:
> > > Wait, you're saying that Macs and Windows clients need to start issuing these
> > new magical ioctl's to Samba/Linux servers? Not a solution, IMO.
> >
> > I think what Jeremy is saying is the other way around: linux programs
> > issuing ioctls that cifs.ko will translate to what SMB uses to handle
> > stream on the wire.
>
> Well ok, but the same question might apply to local applications,
> or local libraries. Will there be a liblinuxsmb3streams.so, just to
> implement these?
Something like that. Remember, streams are not a part of POSIX
(and IMHO nor should they be :-).
next prev parent reply other threads:[~2018-08-29 19:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 13:51 Streams support in Linux Matthew Wilcox
2018-08-25 14:47 ` Al Viro
2018-08-25 15:51 ` Matthew Wilcox
2018-08-25 18:00 ` Al Viro
2018-08-25 20:57 ` Matthew Wilcox
2018-08-25 22:36 ` Al Viro
2018-08-26 1:03 ` Steve French
2018-08-27 17:05 ` Jeremy Allison
2018-08-27 17:41 ` Jeremy Allison
2018-08-27 18:21 ` Matthew Wilcox
2018-08-27 18:45 ` Al Viro
2018-08-27 19:06 ` Jeremy Allison
2018-08-28 0:45 ` Theodore Y. Ts'o
2018-08-28 1:07 ` Steve French
2018-08-28 18:12 ` Jeremy Allison
2018-08-28 18:32 ` Steve French
2018-08-28 18:40 ` Jeremy Allison
2018-08-28 19:43 ` Steve French
2018-08-28 19:47 ` Jeremy Allison
2018-08-28 20:43 ` Steve French
2018-08-28 20:47 ` Jeremy Allison
2018-08-28 20:51 ` Steve French
2018-08-28 21:19 ` Stefan Metzmacher
2018-08-28 21:22 ` Jeremy Allison
2018-08-28 21:23 ` Steve French
2018-08-29 5:13 ` Ralph Böhme
2018-08-29 13:46 ` Tom Talpey
2018-08-29 13:54 ` Aurélien Aptel
2018-08-29 15:02 ` Tom Talpey
2018-08-29 16:00 ` Jeremy Allison [this message]
2018-08-29 15:59 ` Jeremy Allison
2018-08-29 18:52 ` Andreas Dilger
2018-08-26 20:30 ` Matthew Wilcox
2018-08-25 16:25 ` Theodore Y. Ts'o
2018-08-27 16:33 ` Jeremy Allison
-- strict thread matches above, loose matches on Subject: below --
2018-09-20 2:06 Shahbaz Youssefi
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=20180829160009.GB114671@jra3 \
--to=jra@samba.org \
--cc=aaptel@suse.com \
--cc=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=ttalpey@microsoft.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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