David Edmondson wrote:
> * [EMAIL PROTECTED] [2008-01-10 11:00:33]
>
>> Peter Memishian wrote:
>>
>>> > As an aside, this design does support using STREAMS to capture
>>> > packets quite neatly as it allows complete packets to be queued up
>>> > on the queue, awaiting their turn on the CPU, while packets are
>>> > delivered to sockets simultaneously. But for many packets, the copy
>>> > is made, given to the promiscuous handler and then the original is
>>> > freed because it doesn't have a local destination.
>>>
>>> Could you expand on where you see that? My read of i_dls_link_rx_common()
>>> is that if there's only one matching dls_impl_t (the promiscuous
>>> listener), the fdi_rx logic will skip the copy.
>>>
>> With build 80:
>>
>> #
>> # dtrace -n 'fbt::copymsgchain:entry{stack();}' -c snoop
>> dtrace: description 'fbt::copymsgchain:entry' matched 1 probe
>> Using device e1000g0 (promiscuous mode)
>>
>
> Is e1000g0 also plumbed under IP? Having IP and snoop means that there
> are two consumers, causing the copy path to be used.
>
Yup, e1000g0 is plumbed under IP.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
