On Mon, 24 May 1999, Mike Smith wrote:
> > > There's also very little need for this under "real" circumstances; some
> > > simple tests have demonstrated we can sustain about 800Mbps throughput
> > > (UDP), and the bottleneck here seems to be checksum calculations, not
> > > copyin/out.
> > >
> > > I really do not know how to describe the problem. But a friend here asks
> > > me how to mmap a network buffer so that there is no need to copy the data
> > > from user space to kernel space. We are not sure whether FreeBSD can
> > > create a device file (mknod) for a network card, and if so,
:In my view, the problem can be described like this.
:
:Some applications need to process data from their VA space, on some
:devices. If the data is going to/from a file, it looks perfectly
:well to copy it into kernel buffers, since the kernel does caching
:and improves disk I/O performance. Howev
> My hope was to map the user's buffer into kernel space so that I could do
> event driven io on the socket without having to context switch to an aiod
> for every io operation. Is this really a bad idea? I am a little
> concerned about running out of kernel address space, but I don't think
> tha
On Fri, 21 May 1999, Mike Smith wrote:
> >
> > I really do not know how to describe the problem. But a friend here asks
> > me how to mmap a network buffer so that there is no need to copy the data
> > from user space to kernel space. We are not sure whether FreeBSD can
> > create a device file
>
> I really do not know how to describe the problem. But a friend here asks
> me how to mmap a network buffer so that there is no need to copy the data
> from user space to kernel space. We are not sure whether FreeBSD can
> create a device file (mknod) for a network card, and if so, we can use t
6 matches
Mail list logo
