search for: autocopy

Normal PDC/BDC isn't possible now. It will be in Samba 3.0 (look in documentation). But you can create substitute solution. For example two idendicaly servers with autocopy of password database, but it isn't PDC/BDC relations. It is two identicaly domains. I have two servers with samba, with two indenticaly password databases and smb.conf. When I have problem with one, I can fastly change server PDC. This maybe widen as two servers (and two domains) in different p...

...t only for TX and temporarily. We pin, read, unpin. > > > Probably not. For several reasons that the page will be not be released soon > or held for a very long period of time or even forever. With zero copy? Well it's pinned until transmit. Takes a while but could be enough for autocopy to work esp since its the packet memory so not reused immediately. > > > > > Your patch is different > > > > - it writes into memory and GUP has known issues with file > > backed memory > > > The ordinary user for vhost is anonymous pages I think?...

...t only for TX and temporarily. We pin, read, unpin. > > > Probably not. For several reasons that the page will be not be released soon > or held for a very long period of time or even forever. With zero copy? Well it's pinned until transmit. Takes a while but could be enough for autocopy to work esp since its the packet memory so not reused immediately. > > > > > Your patch is different > > > > - it writes into memory and GUP has known issues with file > > backed memory > > > The ordinary user for vhost is anonymous pages I think?...

...temporarily. We pin, read, unpin. >> >> Probably not. For several reasons that the page will be not be released soon >> or held for a very long period of time or even forever. > > With zero copy? Well it's pinned until transmit. Takes a while > but could be enough for autocopy to work esp since > its the packet memory so not reused immediately. > >>> Your patch is different >>> >>> - it writes into memory and GUP has known issues with file >>> backed memory >> >> The ordinary user for vhost is anonymous pages I th...

We have an existing "management system" of sorts, based on rdist. I''d like to know the best way to migrate it to using puppet. Currently, we have a local binaries tree, rdisted out nightly. We also make use of rdist''s extra capability to trigger scripts when and if named files are updated. I''m not sure what the best method would be, of converting this to

On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote: > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote: > > > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > > > > > It was noticed that the copy_user()

On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote: > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote: > > > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > > > > > It was noticed that the copy_user()

...gt; > > > > > Probably not. For several reasons that the page will be not be released soon > > > or held for a very long period of time or even forever. > > > > With zero copy? Well it's pinned until transmit. Takes a while > > but could be enough for autocopy to work esp since > > its the packet memory so not reused immediately. > > > > > > Your patch is different > > > > > > > > - it writes into memory and GUP has known issues with file > > > > backed memory > > > > > &gt...

...gt; > > > > > Probably not. For several reasons that the page will be not be released soon > > > or held for a very long period of time or even forever. > > > > With zero copy? Well it's pinned until transmit. Takes a while > > but could be enough for autocopy to work esp since > > its the packet memory so not reused immediately. > > > > > > Your patch is different > > > > > > > > - it writes into memory and GUP has known issues with file > > > > backed memory > > > > > &gt...