2005/11/4, kamal kc <[EMAIL PROTECTED]>:
>
> > > for my compression/decompression i use string
> > tables and temporary
> > > buffers which take about 14KB of memory per
> > packet.
> >
> > If you're allocating 14 KB of data just to send
> > (approximately) 1.4 KB
> > and then you throw away the 1
> - Am I not following the correct procedures to
> allocate and deallocate memory in kernel space ??
> - Or is the problem elsewhere ??
You didn't say whether you've checked your code for buffer
overruns.
If the fault is happening in seemingly unrelated parts of
the kernel with your module is e
On 2005-11-03 22:56, kamal kc <[EMAIL PROTECTED]> wrote:
>>> for my compression/decompression i use string tables and
>>> temporary buffers which take about 14KB of memory per
>>> packet.
>>
>> If you're allocating 14 KB of data just to send
>> (approximately) 1.4 KB
>> and then you throw away the
> > for my compression/decompression i use string
> tables and temporary
> > buffers which take about 14KB of memory per
> packet.
>
> If you're allocating 14 KB of data just to send
> (approximately) 1.4 KB
> and then you throw away the 14 KB immediately, it
> sounds terrible.
yes that's true.
On 2005-11-02 18:39, kamal kc <[EMAIL PROTECTED]> wrote:
> dear everybody,
>
> i am trying to compress/decompress ip packets.
> for this i have implemented the adaptive lzw compression.
> i put the code in the ip_output.c and do my compression/decompression
> just before the if_output() function ca
kamal kc wrote:
i am trying to compress/decompress ip packets.
for this i have implemented the adaptive lzw compression.
i put the code in the ip_output.c and do my compression/decompression
just before the if_output() function call so that i won't interfere with
the ip processing of the kernel.
