Displaying 7 results from an estimated 7 matches for "smb_context".
2016 Oct 28
0
Samba and BTRFS server-side copy
...r[4096];
size_t buffer_size;
ssize_t res;
char *p;
gboolean succeeded;
smbc_open_fn smbc_open;
smbc_read_fn smbc_read;
smbc_write_fn smbc_write;
smbc_close_fn smbc_close;
from_file = NULL;
to_file = NULL;
succeeded = FALSE;
smbc_open = smbc_getFunctionOpen (backend->smb_context);
smbc_read = smbc_getFunctionRead (backend->smb_context);
smbc_write = smbc_getFunctionWrite (backend->smb_context);
smbc_close = smbc_getFunctionClose (backend->smb_context);
Which clearly doesn't use the splice call. That's broken.
If there's anyone on the Gnome gvfs...
2016 Oct 28
3
Samba and BTRFS server-side copy
On Thu, 27 Oct 2016 16:57:13 -0700, Jeremy Allison <jra at samba.org>
wrote :
> On Fri, Oct 28, 2016 at 01:42:35AM +0200, Saint Germain via samba
> wrote:
> > On Thu, 27 Oct 2016 16:27:05 -0700, Jeremy Allison <jra at samba.org>
> > > if you see any of these then it happened.
> >
> > Ok I understand how to check that it happened, but how can I make
2016 Oct 28
3
Samba and BTRFS server-side copy
...ows servers,
> * let's do the same here to achieve reasonable performance. (#588391)
> *
> * TODO: port to pull mechanism (#592468)
> */
> if (bytes_requested > 65534)
> bytes_requested = 65534;
>
> smbc_read = smbc_getFunctionRead (op_backend->smb_context);
> res = smbc_read (op_backend->smb_context, (SMBCFILE *)handle, buffer, bytes_requested);
>
> which is also completely broken and wrong. The read call
> can take any arbitrary size and the both the libsmbclient
> SMB1 and SMB2 engines will break this down into as many
> si...
2016 Oct 28
2
Samba and BTRFS server-side copy
...eve reasonable performance.
>>> (#588391) *
>>> * TODO: port to pull mechanism (#592468)
>>> */
>>> if (bytes_requested > 65534)
>>> bytes_requested = 65534;
>>>
>>> smbc_read = smbc_getFunctionRead (op_backend->smb_context);
>>> res = smbc_read (op_backend->smb_context, (SMBCFILE *)handle,
>>> buffer, bytes_requested);
>>>
>>> which is also completely broken and wrong. The read call
>>> can take any arbitrary size and the both the libsmbclient
>>> SMB1 and S...
2016 Oct 28
0
Samba and BTRFS server-side copy
...do the same here to achieve reasonable performance.
> > (#588391) *
> > * TODO: port to pull mechanism (#592468)
> > */
> > if (bytes_requested > 65534)
> > bytes_requested = 65534;
> >
> > smbc_read = smbc_getFunctionRead (op_backend->smb_context);
> > res = smbc_read (op_backend->smb_context, (SMBCFILE *)handle,
> > buffer, bytes_requested);
> >
> > which is also completely broken and wrong. The read call
> > can take any arbitrary size and the both the libsmbclient
> > SMB1 and SMB2 engines will b...
2016 Nov 02
0
Samba and BTRFS server-side copy
...t;>> (#588391) *
> >>> * TODO: port to pull mechanism (#592468)
> >>> */
> >>> if (bytes_requested > 65534)
> >>> bytes_requested = 65534;
> >>>
> >>> smbc_read = smbc_getFunctionRead (op_backend->smb_context);
> >>> res = smbc_read (op_backend->smb_context, (SMBCFILE *)handle,
> >>> buffer, bytes_requested);
> >>>
> >>> which is also completely broken and wrong. The read call
> >>> can take any arbitrary size and the both the libsmbclien...
2016 Nov 02
2
Samba and BTRFS server-side copy
...>>>>> * TODO: port to pull mechanism (#592468)
>>>>> */
>>>>> if (bytes_requested > 65534)
>>>>> bytes_requested = 65534;
>>>>>
>>>>> smbc_read = smbc_getFunctionRead (op_backend->smb_context);
>>>>> res = smbc_read (op_backend->smb_context, (SMBCFILE *)handle,
>>>>> buffer, bytes_requested);
>>>>>
>>>>> which is also completely broken and wrong. The read call
>>>>> can take any arbitrary size and the both...