Re: Socket NKE performance
Re: Socket NKE performance
- Subject: Re: Socket NKE performance
- From: Stéphane Sudre <email@hidden>
- Date: Wed, 11 Jun 2003 11:52:29 +0200
On jeudi, juin 5, 2003, at 19:35 Europe/Paris, Joshua Graessley wrote:
On Thursday, June 5, 2003, at 7:33, Stiphane Sudre wrote:
I'm testing what kind of performance I can get from a Socket NKE
communication from a Kernel Extension to a user land application.
I set the recv_space of the socket to be 224 KB in the Kernel
In the application, I'm using a CFSocket to read the data when
available.
To communicate with the application I'm sbappending 32 Bytes data
using the same kind of code that the NKE tcpdumper sample code.
My unrealistic dream is to reach a peak of 1 MB/s. But 300 KB/s would
already be fair.
From the test I'm making, the performance can just reach 25 KB/s. Is
this not a bit weak compared to what should be expected?
Is there a reason you're only writing 32 bytes at a time? Are you
calling sorwakeup after each time that you write 32 bytes?
It looks like that sending more data at a time is leading to better
performance.
This leads to a somewhat stranger but faster behavior.
Instead of having:
Data sent -> Data sent -> Data sent -> ...
it's now:
Data sent -> Data not sent -> 2 Data sent -> Data sent -> ....
Thanks for the various answers which leads me to find this solution.
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.