All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan (metze) Metzmacher" <metze-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	samba-technical
	<samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org>
Subject: Re: [PATCH 2/2] Allow setting per-file compression via SMB2/3
Date: Fri, 11 Oct 2013 12:57:11 +0200	[thread overview]
Message-ID: <5257D987.3090709@samba.org> (raw)
In-Reply-To: <CAH2r5mvHo4v4uKQfFc-vPtnYt1E8OvbhspskdfNezMbyYFq5KA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Am 11.10.2013 05:00, schrieb Steve French:
> Allow cifs/smb2/smb3 to return whether or not a file is compressed
> via lsattr, and allow SMB2/SMB3 to set the per-file compression
> flag ("chattr +c filename" on an smb3 mount).
> 
> A followon patch will do this for cifs
> 
> Windows users often set the compressed flag (it can be
> done from the desktop and file manager).  David Disseldorp
> has patches to Samba server to support this (at least on btrfs)
> which are complementary to this.
> 
> As Metze suggested I split out the part of the patch
> which fixed up the length calculation in the
> SMB2_ioctl worker function as it is more general
> and not compression specific enablement (I
> just noticed the problem when doing this patch).

Thanks!

metze

      parent reply	other threads:[~2013-10-11 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11  3:00 [PATCH 2/2] Allow setting per-file compression via SMB2/3 Steve French
     [not found] ` <CAH2r5mvHo4v4uKQfFc-vPtnYt1E8OvbhspskdfNezMbyYFq5KA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-11 10:57   ` Stefan (metze) Metzmacher [this message]

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=5257D987.3090709@samba.org \
    --to=metze-eunubhrolfbytjvyw6ydsg@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.