On Wed, 20 Oct 2004, Julian Elischer wrote:
> Now that we have real threads, it shuld be possible to write an aio
> library that is
> implemented by having a bunch of underlying threads..
Do you mean the kernel only threads when the single threaded user process
has several threads in kernel ? As
On Wed, 20 Oct 2004, Christopher M. Sedore wrote:
> > > > While the developing my server nginx, I found the POSIX aio_*
> > > > operations
> > > > uncomfortable. I do not mean a different programming style, I mean
> > > > the aio_read() and aio_write() drawbacks - they have no
> > scatter-gather
>
On Wed, 20 Oct 2004, Ronald F. Guilmette wrote:
> > and they require too many syscalls.
> >E.g, the reading requires
> >*) 3 syscalls for ready data: aio_read(), aio_error(), aio_return()
> >*) 5 syscalls for non-ready data: aio_read(), aio_error(),
> > waiting for notification, then aio_error()
> What I didn't understand is why I am stating src-ip 0xfff as the mask. I
> mean in my bw limiting rules destionation ips (IP1, IP2 ...) should be the
> one that create dynamic pipes whose bw is 100kbits/s for each pipe. But I
> give src-ip 0xfff. Shouldn't the right way for that is to us
On Wed, Oct 20, 2004 at 07:53:28AM -0700, Yong Chu Eu (Ñî×ÓÓÓ) wrote:
> i am try to stream from freeBSD multicast router(without kame but with
> pim6sd,route6d)to MN throught Access Point which are redhat. There is a
> bridge between eth0 and wlan0 at software Access Point. There problem is i
> can
Igor Sysoev wrote:
On Sun, 17 Oct 2004, Ronald F. Guilmette wrote:
I'm sitting here looking at that man pages for aio_read and aio_write,
and the question occurs to me: ``Home come there is no such thing as
an aio_connect function?''
There are clearly cases in which one would like to perform r
In message <[EMAIL PROTECTED]>, you wrote:
>> There are clearly cases in which one would like to perform reads
>> asynchronously, but likewise, there are cases where one might like
>> to also perform socket connects asynchronously. So how come no
>> aio_connect?
>
>In FreeBSD you can do connect(
> From: Igor Sysoev [mailto:[EMAIL PROTECTED]
> Subject: RE: aio_connect ?
>
> On Wed, 20 Oct 2004, Christopher M. Sedore wrote:
>
> > > While the developing my server nginx, I found the POSIX aio_*
> > > operations
> > > uncomfortable. I do not mean a different programming style, I mean
> >
Garrett Wollman wrote:
< said:
That's it for now... just aio_connect() and aio_accept(). If I think of
something else, I'll let you know.
[lots of Big Picture(R) stuff elided]
This is certainly an interesting model of program design. However,
some caution is advised. Here are the most s
In message <[EMAIL PROTECTED]>, you wrote:
>< said:
>
>> That's it for now... just aio_connect() and aio_accept(). If I think of
>> something else, I'll let you know.
>
>[lots of Big Picture(R) stuff elided]
>
>This is certainly an interesting model of program design.
It is very gentlemanly of
On Wed, 20 Oct 2004, Christopher M. Sedore wrote:
> > While the developing my server nginx, I found the POSIX aio_*
> > operations
> > uncomfortable. I do not mean a different programming style, I mean
> > the aio_read() and aio_write() drawbacks - they have no scatter-gather
> > capabilities (aio
In message <[EMAIL PROTECTED]>, you wrote:
>Sorry, but there is nothing in FreeBSD that will let you program in the
>method you would like to do...
Well, _if_ there were a full and complet family of aio_*() functions
implemented in the FreeBSD kernel, _then_ I could indeed program in
the style I
Hello,
I have a weird problem with a GRE tunnel, the setup is as follows;
gre0: flags=b051 mtu
1476
tunnel inet 213.67.20.137 --> 194.145.248.113
inet 194.145.248.138 --> 194.145.248.137 netmask 0xfffc
And I've tried both w/ and w/o the link1 option mention
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Igor Sysoev
> Subject: Re: aio_connect ?
>
[...]
> While the developing my server nginx, I found the POSIX aio_*
> operations
> uncomfortable. I do not mean a different programming style, I mean
> the aio_read() and aio_writ
On Sun, 17 Oct 2004, Ronald F. Guilmette wrote:
> I'm sitting here looking at that man pages for aio_read and aio_write,
> and the question occurs to me: ``Home come there is no such thing as
> an aio_connect function?''
>
> There are clearly cases in which one would like to perform reads
> async
On Wed, 20 Oct 2004, Vladimir Terziev wrote:
> In fact i can't even predict the name of the interface via which the traffic
> will be routed, because my VPN is based on VTUN servers. They choose the next free
> tun device, respectively interface, when the VPN connection is established bete
on Wed, 20 Oct 2004 07:53:28 -0700, Yong Chu Eu <[EMAIL PROTECTED]> said:
>
> i am try to stream from freeBSD multicast router(without kame but with
> pim6sd,route6d)to MN throught Access Point which are redhat. There is a
> bridge between eth0 and wlan0 at software Access Point. There problem
< said:
> That's it for now... just aio_connect() and aio_accept(). If I think of
> something else, I'll let you know.
[lots of Big Picture(R) stuff elided]
This is certainly an interesting model of program design. However,
some caution is advised. Here are the most significant issues:
- Fre
i am try to stream from freeBSD multicast router(without kame but with
pim6sd,route6d)to MN throught Access Point which are redhat. There is a
bridge between eth0 and wlan0 at software Access Point. There problem is i
cannot even start streaming from vls, the error message i paste as below .
I can
on Tue, 19 Oct 2004 03:41:08 -0700 (PDT), Yong Chu Eu <[EMAIL PROTECTED]> asked:
> When i install freeBSD 4.10 without kame code, my multicast function on
> router fail. i try to stream multicast video(vls) from router to vlc
> player at client?
You may need to provide more information:
How
> I read the Quagga documentation a lot of times, but i couldn't find any clue
> how to manipulated metrics when the traffic comes from distinct neighbour. Could you
> help me with this, please ?
offset-list command is mentioned in ripd documentation.
But it seems for me, it is not impleme
In fact i can't even predict the name of the interface via which the traffic
will be routed, because my VPN is based on VTUN servers. They choose the next free tun
device, respectively interface, when the VPN connection is established beteen 2 peers.
I read the Quagga documentat
22 matches
Mail list logo