When the date was Friday 19 August 2005 19:51, Jesse Brandeburg wrote:
> included netdev...
>
> On Wed, 17 Aug 2005, Ming Zhang wrote:
> > Hi folks
> >
> > We ran into this problem when running jumbo frame with iscsi over e1000.
> > the MTU1500 is fine while jumbo frame can stably reproduce this e
On Fri, 2005-08-19 at 19:02 +0200, Andi Kleen wrote:
> > I guess we need to approach the memory manager guys and ask them why the
> > current kernels are having so much trouble getting contiguous memory.
>
> Because memory fragments.
>
> The only long term reliable way is to not allocate buffer
Jesse Brandeburg wrote:
included netdev...
On Wed, 17 Aug 2005, Ming Zhang wrote:
Hi folks
We ran into this problem when running jumbo frame with iscsi over e1000.
the MTU1500 is fine while jumbo frame can stably reproduce this error.
when meet this error, as reported in iet list, the box
> I guess we need to approach the memory manager guys and ask them why the
> current kernels are having so much trouble getting contiguous memory.
Because memory fragments.
The only long term reliable way is to not allocate buffers > PAGE_SIZE.
The stack supports paged skbs for that.
-Andi
-
T
This is first reported on IET list and then i redo the test with vanilla
2.6.12.4 kernel and everything went fine.
so i suspect if there are special case caused by vendor kernel.
is this 32KB ATOMIC ram allocation request only available in jumbo frame
case? since the regular MTU case goes fine.
included netdev...
On Wed, 17 Aug 2005, Ming Zhang wrote:
Hi folks
We ran into this problem when running jumbo frame with iscsi over e1000.
the MTU1500 is fine while jumbo frame can stably reproduce this error.
when meet this error, as reported in iet list, the box still has >600MB
ram free
