similar to: NT4 Performance Issues

Greetings, I am setting up Dovecot 1.0.15 on my home Fedora Core 8 pc ONLY to access my mail archives across several mail clients. No access from the internet is possible or needed here. I cannot log in with any client, the login always fails. The reason, as I understand, is that when dovecot starts it doesn't read any user name from the userdb file, so when I try to login it doesn't

When using the -z and -B65536 options together, sometimes there is file corruption. Client and server are both compiled against zlib 1.1.4, so the gzip corruption shouldn't be there, right? With -z and -B32768 there is an error, but it is detected in a different way. With -B65536 and without -z all seems to be going OK. With -B16384 and with -z all seems to be going OK. I'm guessing

<expletive deleted> My roaming profiles keep "forgetting" they exist on my W2K boxen. It doesn't occur server-side, as other W2K clients log in fine. But, once one of the clients has forgotten about roaming profiles, it usually takes a re-install to make it remember them... and then, only temporarily. (Except on one machine that's worked fine from the get-go.) I even

Hi, I have a Fedora 14 x86_64 computer. I run dovecot 2.0.12 on it, only to keep a local imap copy of all my email, in maildir format. A couple days ago the hard disk broke, so I bought a new one, and reinstalled Fedora 14 x86_64 with all the updates. Then I copied all the maildirs from a backup to the new drive. But I can't access email now. No matter how I change sticky bits or ownership

I'm attempting to upgrade to kernel-smp-2.4.21-27.0.4.EL (x86_64) on a Dell 1850. The new kernel is panicing on reboot. When comparing against the current working kernel, I just noticed that we're currently running the "UP" kernel: [root at polaris root]# uname -srvp Linux 2.4.21-27.0.2.EL #1 SMP Wed Jan 19 11:49:43 CST 2005 x86_64 First question... why is the kernel

Server host config: Slackware 8.0 (custom boot scripts) glibc-2.2.3 gcc-2.95.3 Linux-2.4.18 Client host config: (same as server) Symptom: session disconnects with no message to client: ============================================================================= phil at antares:/home/phil 153> ssh -V OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f phil at antares:/home/phil 154>

When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4 to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little while (of inactivity?) I get the following message on the client terminal: Disconnecting: protocol error: rcvd type 98 Looking further, this message is actually caused by the SSH daemon. However, I'm at a loss to determine why sshd is doing this. I attach

On Thu, 2011-12-08 at 11:53 +0800, 陳韋任 wrote: > > I am looking appropriate Benchmarking for the assessment of automatic > > parallelization project. What Benchmarking do you suggest me? > > Do you mean auto-parallelization or auto-vectorization? If it's the latter, I > sugguest you find scientific or graphic applications. For auto-vectorization, look at:

The functionality is identical to the one currently open coded in device-dax. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/dax/dax-private.h | 4 ---- drivers/dax/device.c | 43 --------------------------------------- 2 files changed, 47 deletions(-) diff --git a/drivers/dax/dax-private.h b/drivers/dax/dax-private.h index a45612148ca0..ed04a18a35be 100644 ---

The functionality is identical to the one currently open coded in device-dax. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/dax/dax-private.h | 4 ---- drivers/dax/device.c | 43 --------------------------------------- 2 files changed, 47 deletions(-) diff --git a/drivers/dax/dax-private.h b/drivers/dax/dax-private.h index b4177aafbbd1..c915889d1769 100644 ---

The functionality is identical to the one currently open coded in device-dax. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/dax/dax-private.h | 4 --- drivers/dax/device.c | 52 +-------------------------------------- 2 files changed, 1 insertion(+), 55 deletions(-) diff --git a/drivers/dax/dax-private.h b/drivers/dax/dax-private.h index a45612148ca0..ed04a18a35be

Hi Hal, > For auto-vectorization, look at: > http://polaris.cs.uiuc.edu/~garzaran/doc/pact11.pdf > http://polaris.cs.uiuc.edu/~maleki1/TSVC.tar.gz > > If you're looking for auto-parallelization, I can ask around. Thanks for the sharing. If that doesn't bother you too much, I would like to know auto-parallelization benchmarks. :p Just curious. I was thinking that

On Thu, Jun 13, 2019 at 11:43:16AM +0200, Christoph Hellwig wrote: > The functionality is identical to the one currently open coded in > device-dax. > > Signed-off-by: Christoph Hellwig <hch at lst.de> > --- > drivers/dax/dax-private.h | 4 --- > drivers/dax/device.c | 52 +-------------------------------------- > 2 files changed, 1 insertion(+), 55

On Tue, Sep 03, 2019 at 10:05:02AM +0200, Miklos Szeredi wrote: > [Cc: virtualization at lists.linux-foundation.org, "Michael S. Tsirkin" > <mst at redhat.com>, Jason Wang <jasowang at redhat.com>] > > It'd be nice to have an ACK for this from the virtio maintainers. > > Thanks, > Miklos Can the patches themselves be posted to the relevant list(s)

On Tue, Sep 03, 2019 at 10:05:02AM +0200, Miklos Szeredi wrote: > [Cc: virtualization at lists.linux-foundation.org, "Michael S. Tsirkin" > <mst at redhat.com>, Jason Wang <jasowang at redhat.com>] > > It'd be nice to have an ACK for this from the virtio maintainers. > > Thanks, > Miklos Can the patches themselves be posted to the relevant list(s)

This patch adds 'DAXDEV_SYNC' flag which is set for nd_region doing synchronous flush. This later is used to disable MAP_SYNC functionality for ext4 & xfs filesystem for devices don't support synchronous flush. Signed-off-by: Pankaj Gupta <pagupta at redhat.com> --- drivers/dax/bus.c | 2 +- drivers/dax/super.c | 13 ++++++++++++- drivers/md/dm.c

This patch adds 'DAXDEV_SYNC' flag which is set for nd_region doing synchronous flush. This later is used to disable MAP_SYNC functionality for ext4 & xfs filesystem for devices don't support synchronous flush. Signed-off-by: Pankaj Gupta <pagupta at redhat.com> --- drivers/dax/bus.c | 2 +- drivers/dax/super.c | 13 ++++++++++++- drivers/md/dm.c

This patch adds 'DAXDEV_SYNC' flag which is set for nd_region doing synchronous flush. This later is used to disable MAP_SYNC functionality for ext4 & xfs filesystem for devices don't support synchronous flush. Signed-off-by: Pankaj Gupta <pagupta at redhat.com> --- drivers/dax/bus.c | 2 +- drivers/dax/super.c | 13 ++++++++++++- drivers/md/dm.c

On Wed 10-04-19 09:38:24, Pankaj Gupta wrote: > This patch introduces 'daxdev_mapping_supported' helper > which checks if 'MAP_SYNC' is supported with filesystem > mapping. It also checks if corresponding dax_device is > synchronous. Virtio pmem device is asynchronous and > does not not support VM_SYNC. > > Suggested-by: Jan Kara <jack at suse.cz> >

There are several places where ZONE_DEVICE struct pages assume a reference count == 1 means the page is idle and free. Instead of open coding this, add a helper function to hide this detail. Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> --- fs/dax.c | 8 ++++---- fs/ext4/inode.c | 2 +- fs/xfs/xfs_file.c | 2 +- include/linux/dax.h | 5 +++++ 4 files changed, 11