similar to: oom killer: gfp=mask=0xd1 - bug w/ EM64T?

Hi Dirk I think there are problems with pg_config, the configure script of RPostgreSQL checks for pg_config and got ¡°checking for pg_config... /usr/bin/pg_config¡±. In Solaris 10u7 X64, three versions of PostgreSQL are installed, there are in /usr/postgres/8.2(8.2.9) and /usr/postgres/8.3(8.3.3), the corresponding bin files are in /usr/postgres/<version>/bin and

Hi, I post this message to the general r-help list hoping anyone within a wider range have suggestions: There are three ways to integration R and postgres, especially on 64bit Microsoft windows Platform, 1. via RODBC package, which has 32 bit and 64 bit version for windows 2. via RPostgres interface, which only has 32bit version currently 3. via plr for Greenplum, which only supports a

Apologies if you received duplicate copies of this Call for Papers. Sincerely, Aravind Menon MBDS 2012 ----------------------------------------------------------------- CALL FOR PAPERS International Workshop on Management of Big Data Systems (MBDS 2012) http://www.cercs.gatech.edu/mbds12 In conjunction with ICAC 2012 http://icac2012.cs.fiu.edu September 21, 2012, San Jose, CA

Apologies if you received duplicate copies of this Call for Papers. Sincerely, Aravind Menon MBDS 2012 ----------------------------------------------------------------- CALL FOR PAPERS International Workshop on Management of Big Data Systems (MBDS 2012) http://www.cercs.gatech.edu/mbds12 In conjunction with ICAC 2012 http://icac2012.cs.fiu.edu September 21, 2012, San Jose, CA

Hello, Will switchning to 64bit distribution (intel EM64T) provide any performance gain to the networking code: routing (lots of rules and big routing tables), scheduling (htb) and iptables? Thank you. -- Anton Glinkov network administrator

Hi all, Just a couple of quick questions. I have a HP DL360 G4 (dual 3.0Ghzprocessors). The processors are EM64T. I am using a TE411P in the system. 1. Should I run the a x86_64 Linux (CentOS) or just go with the plain old 32 bit version? 2. This being a dual processor system, should I turn on or off hyper thrreading? Thanks..... -------------- next part -------------- An HTML attachment was

I'm looking to install Asterisk on an EM64T Dell 1850. PERC raid 1, 1GB ram, single 3Ghz Xeon. Any red flags or anything I should know? Should I bother installing a 64 bit OS? (gentoo-amd64)? Does asterisk work in 64 bit mode? Should I turn hyper threading off? Etc?

Hi, A new version (2.0.8-2.centos) for yum has been pushed to the mirrors for testing before going into the main tree. This release only includes a small fix for EM64T machines running the x86_64 version of CentOS 3: the ia32e architecture is now recognized for yum as an compatible architecture name. The only CentOS ia32e.rpm are the kernel and kernel-unsupported rpms. No one has reported the

Hi all, My Ct's box is RH 3.0 SMP kernel EM64T. They are asking if OCFS for SMP (EM64T) is available or not. In following site, we can not see OCFS for SMP (EM64T). http://oss.oracle.com/projects/ocfs/files/RedHat/RHEL3/x86_64/1.0.14-1/ ---------- ocfs-2.4.21-EL-1.0.14-1.ia32e.rpm OCFS driver for kernel version 2.4.21-27.EL and higher (EM64T) ocfs-2.4.21-EL-1.0.14-1.src.rpm OCFS driver

Hi Guys Im trying to complile Asterisk on my new dual Xeon 3.0ghz EM64T machine. Im running Debian 3.1, and have installed the 2.6.8-11-em64t-p4-smp kernel (and headers). The system is working fine and is detecting both CPU's (4 actually, with hyperthreading). But when I try to compile Zaptel, Im getting this error: /lib/modules/2.6.8-11-em64t-p4-smp? /build make -C

Signed-off-by: Nick Piggin <npiggin@suse.de> -- Index: linux-2.6/fs/btrfs/compression.c =================================================================== --- linux-2.6.orig/fs/btrfs/compression.c +++ linux-2.6/fs/btrfs/compression.c @@ -478,7 +478,7 @@ static noinline int add_ra_bio_pages(str goto next; } - page = alloc_page(mapping_gfp_mask(mapping) | GFP_NOFS); + page =

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote: > On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote: > > I think it is just better to follow kernel convention and have > > allocation functions include the GFP because it is a clear signal to > > the user that there is an allocation hidden inside the API. The whole > > point of gfp is not to

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote: > On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote: > > I think it is just better to follow kernel convention and have > > allocation functions include the GFP because it is a clear signal to > > the user that there is an allocation hidden inside the API. The whole > > point of gfp is not to

On 2023-01-18 18:00, Jason Gunthorpe wrote: > Change the sg_alloc_table_from_pages() allocation that was hardwired to > GFP_KERNEL to use the gfp parameter like the other allocations in this > function. > > Auditing says this is never called from an atomic context, so it is safe > as is, but reads wrong. I think the point may have been that the sgtable metadata is a

On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote: > I think it is just better to follow kernel convention and have > allocation functions include the GFP because it is a clear signal to > the user that there is an allocation hidden inside the API. The whole > point of gfp is not to have multitudes of every function for every > allocation mode. Well, having GFP

Dear mailing-list members, In the days of cheap RAM and microarray applications feasting on memory, 64-bit computers become more and more useful - to actually make use of memory beyond the magic 4GB border. I would like to report the success of running 64-bit R on an Intel Xeon EM64T machine under Linux. Just like on an AMD Opteron, R v2.0.0 compiles fine (and out of the box) and is happily

On Fri, Jan 06, 2023 at 05:15:28PM +0000, Robin Murphy wrote: > On 2023-01-06 16:42, Jason Gunthorpe wrote: > > The internal mechanisms support this, but instead of exposting the gfp to > > the caller it wrappers it into iommu_map() and iommu_map_atomic() > > > > Fix this instead of adding more variants for GFP_KERNEL_ACCOUNT. > > FWIW, since we *do* have two

On Fri, Jan 06, 2023 at 05:15:28PM +0000, Robin Murphy wrote: > On 2023-01-06 16:42, Jason Gunthorpe wrote: > > The internal mechanisms support this, but instead of exposting the gfp to > > the caller it wrappers it into iommu_map() and iommu_map_atomic() > > > > Fix this instead of adding more variants for GFP_KERNEL_ACCOUNT. > > FWIW, since we *do* have two

btree_releasepage is a callback and can be passed unknown gfp flags and then they may end up in kmem_cache_alloc called from alloc_extent_state, slab allocator will BUG_ON when there is HIGHMEM or DMA32 flag set. This may happen when btrfs is mounted from a loop device, which masks out __GFP_IO flag. The check in try_release_extent_state 3399 if ((mask & GFP_NOFS) ==

hi, With XEN enabled in mainline kernel 2.6.37 configured for nouveau, X failed with familiar symptoms. Found drm-tree did not have the TTM_MEMTYPE_FLAG_NEEDS_IOREMAP or the drm_scatter patches. Applied these patches (generated from my working 2.6.32.18 xen kernel with 2.6.35.4 drm-tree backported) to the 2.6.37 mainline kernel. Now starting X in dom0 invokes the OOM killer! Bare boot works, as