search for: thouroughly

...this patchset is ready :) > > > > Also it's ready to the level where benchmarking is possible, right? I > > don't think you should wait until we finish polishing up commit > > messages. > > My point is that I haven't even found time yet to test this > thouroughly :( If my experience shows anything, it's unlikely we'll get appropriate testing without code being upstream first. That's why I pushed on with sparse tagging btw. This way we can be reasonably sure we didn't miss some path. -- MST

...this patchset is ready :) > > > > Also it's ready to the level where benchmarking is possible, right? I > > don't think you should wait until we finish polishing up commit > > messages. > > My point is that I haven't even found time yet to test this > thouroughly :( If my experience shows anything, it's unlikely we'll get appropriate testing without code being upstream first. That's why I pushed on with sparse tagging btw. This way we can be reasonably sure we didn't miss some path. -- MST

"Michael S. Tsirkin" <mst at redhat.com> wrote on 20/08/2014 01:57:10 PM: > > Results: > > > > Netperf, 1 vm: > > The polling patch improved throughput by ~33% (1516 MB/sec -> 2046 MB/sec). > > Number of exits/sec decreased 6x. > > The same improvement was shown when I tested with 3 vms running netperf > > (4086 MB/sec -> 5545

"Michael S. Tsirkin" <mst at redhat.com> wrote on 20/08/2014 01:57:10 PM: > > Results: > > > > Netperf, 1 vm: > > The polling patch improved throughput by ~33% (1516 MB/sec -> 2046 MB/sec). > > Number of exits/sec decreased 6x. > > The same improvement was shown when I tested with 3 vms running netperf > > (4086 MB/sec -> 5545

...an entire CD. The error I get is FLAC_STREAM_DECODER_ERROR_LOST_SYNC. They played until recently using WinAmp and PhatNoise. They will not decode, returning a 0 error. I recently re-installed Windoze (XP Pro) if this might be a cause, but many of the files I had before the reinstall still do play. Thouroughly anti-vi'ed using Trend Micro's Housecall, no virus. If you know what might have caused this is there a simple fix? Otherwise I'll have to re-wav and re-flac everything. Several wasted hours and one unhappy camper if I can't fix this. FLAC/OGG thru HI-FI users - I have only heard...

...that actually point me in this direction, so it's more of a "feeling" :-/ I just wanted to ask if that (users being member of a huge number of AD groups and thus there Kerberos ticket getting really big) can be at all a problem with Samba/Winbind and that I should investigate more thouroughly along this line? -- CU, Joe

On Mon, Dec 01, 2014 at 01:02:58PM +0100, Cornelia Huck wrote: > On Mon, 1 Dec 2014 13:46:45 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > On Mon, Dec 01, 2014 at 12:33:15PM +0100, Cornelia Huck wrote: > > > On Mon, 1 Dec 2014 11:26:58 +0200 > > > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > >

On Mon, Dec 01, 2014 at 01:02:58PM +0100, Cornelia Huck wrote: > On Mon, 1 Dec 2014 13:46:45 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > On Mon, Dec 01, 2014 at 12:33:15PM +0100, Cornelia Huck wrote: > > > On Mon, 1 Dec 2014 11:26:58 +0200 > > > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > >

...o it's ready to the level where benchmarking is possible, right? I > > > > don't think you should wait until we finish polishing up commit > > > > messages. > > > > > > My point is that I haven't even found time yet to test this > > > thouroughly :( > > > > If my experience shows anything, it's unlikely we'll get appropriate > > testing without code being upstream first. > > That's why I pushed on with sparse tagging btw. > > This way we can be reasonably sure we didn't miss some path. > &g...

...o it's ready to the level where benchmarking is possible, right? I > > > > don't think you should wait until we finish polishing up commit > > > > messages. > > > > > > My point is that I haven't even found time yet to test this > > > thouroughly :( > > > > If my experience shows anything, it's unlikely we'll get appropriate > > testing without code being upstream first. > > That's why I pushed on with sparse tagging btw. > > This way we can be reasonably sure we didn't miss some path. > &g...

...ode path isn't taken. I'm trying to get a handle on where I should be looking to fix the problem. If your saying that the gas version in FLAC CVS has been validated, the easiest solution is to just use that one. Otherwise I need to go back to the Apple version. Presumably that one has been thouroughly checked? cheers, John -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 282 bytes Desc: not available Url : http://lists.xiph.org/pipermail/flac-dev/attachments/20050121/6dae74f7/attachment.pgp

Hi all, in respect of the "recent" CentOS forum thread, (found here https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=28126&forum=38) I wrote a "Sun/Oracle Java Installation Manual for CentOS 5" - posted on my Wiki Profile page, http://wiki.centos.org/MilosBlazevic?action=show and would like update the Java Wiki page with this content. Of

Hello , I am trying to connect linux 7.2 client with the Windows KDC using kinit command . I am getting error line. "kinit(v5): Clock skew too great while getting initial credentials" Can you reply me what went wrong. Thanks and regards, Prerit. -------------- next part -------------- HTML attachment scrubbed and removed

Hello, i am actually working on samba 3.0rc2 (with OpenLDAP) and i have problems joigning a workstation to the domain. With samba 2.2, a user could be in the NT "Domain Admins" group if he was a member of the unix group that has a gid=512. This user could then join any windows workstation with his account. How can we do this now with samba 3.0 ? When i tried to create a mapping group

I'm contemplating the upgrade for my production network from (Red Hat Enterprises') version 3.0.2 to 3.0.7 (which is the latest from Red Hat). So I start to peruse the changelog and I see this: "Syntax errors in the OpenLDAP schema file (samba.schema)." as one of 4 bullet items at the top of the Samba 3.0.7 changelog. This has me a bit concerned. My production environment is

From: Razya Ladelsky > "Michael S. Tsirkin" <mst at redhat.com> wrote on 20/08/2014 01:57:10 PM: > > > > Results: > > > > > > Netperf, 1 vm: > > > The polling patch improved throughput by ~33% (1516 MB/sec -> 2046 MB/sec). > > > Number of exits/sec decreased 6x. > > > The same improvement was shown when I tested with 3

...ce here? > > > > That this patchset is ready :) > > Also it's ready to the level where benchmarking is possible, right? I > don't think you should wait until we finish polishing up commit > messages. My point is that I haven't even found time yet to test this thouroughly :(

...> > > > Also it's ready to the level where benchmarking is possible, right? I > > > don't think you should wait until we finish polishing up commit > > > messages. > > > > My point is that I haven't even found time yet to test this > > thouroughly :( > > If my experience shows anything, it's unlikely we'll get appropriate > testing without code being upstream first. > That's why I pushed on with sparse tagging btw. > This way we can be reasonably sure we didn't miss some path. I know that I'm likely the o...

...ce here? > > > > That this patchset is ready :) > > Also it's ready to the level where benchmarking is possible, right? I > don't think you should wait until we finish polishing up commit > messages. My point is that I haven't even found time yet to test this thouroughly :(

...> > > > Also it's ready to the level where benchmarking is possible, right? I > > > don't think you should wait until we finish polishing up commit > > > messages. > > > > My point is that I haven't even found time yet to test this > > thouroughly :( > > If my experience shows anything, it's unlikely we'll get appropriate > testing without code being upstream first. > That's why I pushed on with sparse tagging btw. > This way we can be reasonably sure we didn't miss some path. I know that I'm likely the o...