Re: wine on Intel Xeon processor

[Ananth M]

Hi
    Thank you
    Our processor is a 64 bit processor.
    I need to check for the Dual Core or not ?

BTW, if possible , can you please send the URL for the other thread that
gives the information about the slower performance in Dual Core machine

Right now, I have RHEL 4.0 in all Xeon processors. I need to install
Windows OS on it , to verify for any issues with RHEL with wine on Xeon
processor. I will try to that in this weekend

Thank you
Regards
Ajay

On 2/10/06, Coleman Kane  wrote:
> On Fri, 2006-02-10 at 10:51 -0600, Tom Spear (Dustin Booker, Dustin
> Navea) wrote:
> > Hi, sorry I didnt reply all so it would go to the wine list.
> >
> > Is your Xeon a dual core, or possibly even 64-bit?  I doubt that 64-bit
> > compared to 32-bit would make a difference, but if the Xeon is a dc, it
> > might, as I recall another thread here saying that they were having
> > problems with a dual core system being slower.
> >
> > The only other thing I can think of (of course I'm not that far along
> > with my programming skill, and I doubt it will make much difference
> > anyway) is what kind of machine the application and the dll were
> > compiled on.  If you have the source for either of those, and have
> > access to a xeon that is running windows (2003 server?) and can compile,
> > i'd suggest trying that, otherwise, I have no clue.
> >
> > HTH
> >
> > Tom
>
> If memory serves me right, many of the dual-core intel chips share some
> on-chip components (such as the total cache). You'd get all of the cache
> lines allocated to one chip in UP, and divided among the cores in SMP.
> There are probably other resources on the chip for which this is the
> case... perhaps that is a source of your slowness?
>
> --
> coleman kane
> > Ananth M wrote:
> > > On 2/10/06, *Ananth M* <[e-mail]
> > > > wrote:
> > > The wine source code was compiled in the Xeon processor
> > >
> > > We had'nt recompiled the kernel with Xeon Processor , we are using
> > > the same that is coming with RHEL 4.0
> > >
> > >
> > >
> > >   Now I compiled the kernel again and used the new kernel Image.
> > >
> > > Still I am getting the same timings
> > > On 2/9/06, *Tom Spear (Dustin Booker, Dustin Navea)* <
> > > [e-mail] <mailto:[e-mail]>> wrote:
> > >
> > >     Are the wine binaries on the Xeon server precompiled (even
> > >     copied from
> > >     the P4 machine), or are they compiled on the Xeon server
>
> itself?
> > >     Also, has the kernel been recompiled with explicit support for
> > >     the Xeon,
> > >     or is it the stock kernel that comes with RHEL 4?
> > >
> > >     Tom
> > >
> > >     Ananth M wrote:
> > >     > Hi All
> > >     >
> > >     >               I have a windows application that calls a
> > >     function (
> > >     >    approximately 10000 times) exported by a third party DLL.
> > >     >                 I have two machines ( one with Intel pentium
>
> 4
> > >     > processor and
> > >     >    other with Intel Xeon processor ) with RHEL 4.0 installed
> > >     on both
> > >     > of these
> > >     >    machine.
> > >     >                If I execute the windows application on the
>
> first
> > >     > machine (one
> > >     >    with Intel pentium 4 processor ) using WINE, the
>
> execution
> > >     time is
> > >     > almost
> > >     >    equal to the execution time in windows machine.
> > >     >                But, if I execute the same application on the
> > >     second
> > >     > machine
> > >     >    (Intel Xeon processor ), the execution time is almost 6
> > >     times to
> > >     > the first
> > >     >    machine.
> > >     >               I am using WINE-0.9.2 and wine is installed by
> > >     > downloading the
> > >     >    wine source code from winehq.org <http://winehq.org/> <
> > >     http://winehq.org/>
> > >     >               Is it a known issue (or )
> > >     >               Do I need to do any additional configuration
> > >     setting to
> > >     > work with
> > >     >    Intel Xeon processor ?
> > >     >
> > >     > Regards
> > >     > Ajay
> > >     >
> > >     >
> > >     >
> > >     >