Eric W. Biederman writes:
> If you are doing a real time task you don't want to very close
> to your performance envelope. If you are hitting the performance
> envelope any small hiccup will cause you to miss your deadline,
> and close to your performance envelope hiccups are virtually certain.
Jes Sorensen writes:
> Albert D Cahalan <[EMAIL PROTECTED]> writes:
[about using huge physical allocations for number crunching]
>> 2. Programming a DMA controller with multiple addresses isn't
>> as fast as programming it with one.
>
> LOL
>
> Consider that allocating the larger block of memory
> "Albert" == Albert D Cahalan <[EMAIL PROTECTED]> writes:
>> bigmem is 'last resort' stuff. I'd much rather it is as now a
>> seperate allocator so you actually have to sit and think and decide
>> to give up on kmalloc/vmalloc/better algorithms and only use it
>> when the hardware sucks
Alb
"Albert D. Cahalan" <[EMAIL PROTECTED]> writes:
> > bigmem is 'last resort' stuff. I'd much rather it is as now a
> > seperate allocator so you actually have to sit and think and
> > decide to give up on kmalloc/vmalloc/better algorithms and
> > only use it when the hardware sucks
>
> It isn't j
> bigmem is 'last resort' stuff. I'd much rather it is as now a
> seperate allocator so you actually have to sit and think and
> decide to give up on kmalloc/vmalloc/better algorithms and
> only use it when the hardware sucks
It isn't just for sucky hardware. It is for performance too.
1. Linux
On Fri, Dec 22, 2000 at 10:39:43PM +0100, Erik Mouw wrote:
> On Fri, Dec 22, 2000 at 02:54:50PM -0700, Jeff V. Merkey wrote:
> > Having a 1 Gigabyte per second fat pipe that runs over a prallel bus
> > fabric with a standard PCI card that costs @ $ 500 and can run LVS
> > and TUX at high speeds
On Fri, Dec 22, 2000 at 11:37:29AM -0800, Tim Wright wrote:
I have been working with SCI since 1994. The people who own
Dolphin and the SCI chipsets also own TRG. We dropped work in
the P6 ccNUMA cards several years back because Intel was
convinced that shared-nothing was the way to go (and
Hi Jeff,
On Fri, Dec 22, 2000 at 11:11:05AM -0700, Jeff V. Merkey wrote:
[...]
> SCI allows machines to create windows of shared memory across a cluster
> of nodes, and at 1 Gigabyte-per-second (Gigabyte not gigabit). I am
> putting a sockets interface into the drivers so Apache, LVS, and
> Pir
On Fri, Dec 22, 2000 at 08:21:37PM +0100, Andi Kleen wrote:
> On Fri, Dec 22, 2000 at 11:35:30AM -0700, Jeff V. Merkey wrote:
> > The real question is how to guarantee that these pages will be contiguous
> > in memory. The slab allocator may also work, but I think there are size
> > constraints o
On Fri, Dec 22, 2000 at 11:35:30AM -0700, Jeff V. Merkey wrote:
> The real question is how to guarantee that these pages will be contiguous
> in memory. The slab allocator may also work, but I think there are size
> constraints on how much I can get in one pass.
You cannot guarantee it after the
On Fri, Dec 22, 2000 at 11:11:05AM -0700, Jeff V. Merkey wrote:
> On Fri, Dec 22, 2000 at 09:39:28AM +0100, Pauline Middelink wrote:
> > On Thu, 21 Dec 2000 around 15:53:39 -0700, Jeff V. Merkey wrote:
>
Pauline/Alan,
I have been studying the SCI code and I think I may have a workaround that
wo
On Fri, Dec 22, 2000 at 09:39:28AM +0100, Pauline Middelink wrote:
> On Thu, 21 Dec 2000 around 15:53:39 -0700, Jeff V. Merkey wrote:
> >
> > Alan,
> >
> > I am looking over the 2.4 bigphysarea patch, and I think I agree
> > there needs to be a better approach. It's a messy hack -- I agree.
>
> (Alan: bootmem allocation just won't do. I need that memory
> in modules which get potentially loaded/unloaded, hence a
> wrapper interface for allowing access to a bootmem allocated
> piece of memory)
Yes, I pointed him at you for 2.4test because you had the code sitting on
top of bootmem whic
On Thu, 21 Dec 2000 around 15:53:39 -0700, Jeff V. Merkey wrote:
>
> Alan,
>
> I am looking over the 2.4 bigphysarea patch, and I think I agree
> there needs to be a better approach. It's a messy hack -- I agree.
Please explain further.
Just leaving it at that is not nice. What is messy?
The
Alan,
I am looking over the 2.4 bigphysarea patch, and I think I agree
there needs to be a better approach. It's a messy hack -- I agree.
:-)
Jeff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the
On Thu, Dec 21, 2000 at 09:32:46PM +, Alan Cox wrote:
> > A question related to bigphysarea support in the native Linux
> > 2.2.19 and 2.4.0 kernels.
> >
> > I know there are patches for this support, but is it planned for
> > rolling into the kernel by default to support Dolphin SCI and
>
> A question related to bigphysarea support in the native Linux
> 2.2.19 and 2.4.0 kernels.
>
> I know there are patches for this support, but is it planned for
> rolling into the kernel by default to support Dolphin SCI and
> some of the NUMA Clustering adapters. I see it there for some
> of
A question related to bigphysarea support in the native Linux
2.2.19 and 2.4.0 kernels.
I know there are patches for this support, but is it planned for
rolling into the kernel by default to support Dolphin SCI and
some of the NUMA Clustering adapters. I see it there for some
of the video a
18 matches
Mail list logo
