Date: Mon, 03 Aug 2009 21:52:04 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Maslan <maslanbsd@gmail.com> Cc: hackers@freebsd.org Subject: Re: sosend() and mbuf Message-ID: <86eirs65gb.fsf@ds4.des.no> In-Reply-To: <319cceca0908031043x6bfe5771wa73553dce922756a@mail.gmail.com> (Maslan's message of "Mon, 3 Aug 2009 17:43:14 %2B0000") References: <319cceca0908030119i3432a495ya60aa431dab0e1b1@mail.gmail.com> <864ospvvkv.fsf@ds4.des.no> <319cceca0908031043x6bfe5771wa73553dce922756a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[please cc: the list] Maslan <maslanbsd@gmail.com> writes: > man 9 sosend: > Data may be sent directly from kernel or user memory via the uio > argument, or as an mbuf chain via top, avoid- ing a data copy. > Only one of the uio or top pointers may be non-NULL Hmm, I missed that part. It never occurred to me to *not* use mbufs. I guess the question is: what is your question? Does your code work? If it doesn't, where and how does it fail? If it does, why are you asking? In any case, 'man 9 sosend' answers the "I can't find useful information on sosend()" part of your email. If you still have questions after reading that, try looking at existing kernel code that uses sosend(9) with iovecs (or with mbufs, if you decide to go that route). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86eirs65gb.fsf>