| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
treatment of 'LIBKSE' as an "old style" knob.
Submitted by: ru
Approved by: re(kensmith)
|
|
|
|
|
|
| |
This introduces the WITHOUT_LIBKSE nob,
and changes WITHOUT_LIBPTHREADS to mean with neither threading libs.
Approved by: re(kensmith)
|
|
|
|
|
|
|
|
|
|
|
|
| |
the threading libraries is built. This simplifies the
logic in makefiles that need to check if the pthreads
support is present. It also fixes a bug where we would
build a threading library that we shouldn't have built:
for example, building with WITHOUT_LIBTHR and the default
value of DEFAULT_THREADING_LIB (libthr) would mistakenly
build the libthr library, but not install it.
Approved by: re (kensmith)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
returns u_int.
Reported by: Javier MartÃn Rueda <jmrueda@diatel.upm.es>
PR: amd64/91799
MFC after: 3 days
|
|
|
|
|
| |
- Don't build ngctl(8) and cached(8) if threading libs aren't built.
- Fix various issues in a cached(8) makefile.
|
|
|
|
|
|
|
|
|
| |
- Increase timeout to 8 seconds (should be made configurable).
Reported by: Ulrich Spoerlein <uspoerlein@gmail.com>
Reported by: Christian Laursen <xi@borderworlds.dk>
PR: kern/104829
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
mdoc(7) warning.
|
|
|
|
|
| |
is (sym)linked to libpthread. Account for this change and
check for MK_LIBTHR instead of MK_LIBC_R where appropriate.
|
|
|
|
| |
on platform.
|
|
|
|
|
|
|
|
| |
http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
The src.conf(5) manpage is to follow in a few days.
Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
|
|
|
|
|
|
|
|
| |
read when 'ggatec create' is used in backticks or its output is piped to
another command.
Submitted by: Paul Schenkeveld
MFC after: 3 days
|
| |
|
|
|
|
| |
MFC after: 1 day
|
|
|
|
|
| |
Reported by: Andrea Campi <andrea+freebsd_cvs_all@webcom.it>
Approved by: re (scottl)
|
|
|
|
| |
Approved by: re (scottl)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change communication protocol to be much more resistant on network
problems and to allow for much better performance.
Better performance is achieved by creating two connections between
ggatec and ggated one for sending the data and one for receiving it.
Every connection is handled by separeted thread, so there is no more
synchronous data flow (send and wait for response), now one threads
sends all requests and another receives the data.
Use two threads in ggatec(8):
- sendtd, which takes I/O requests from the kernel and sends them to the
ggated daemon on the other end;
- recvtd, which waits for ggated responses and forwards them to the kernel.
Use three threads in ggated(8):
- recvtd, which waits for I/O requests and puts them onto incoming queue;
- disktd, which takes requests from the incoming queue, does disk operations
and puts finished requests onto outgoing queue;
- sendtd, which takes finished requests from the outgoing queue and sends
responses back to ggatec.
Because there were major changes in communication protocol, there is no
backward compatibility, from now on, both client and server has to run
on 5.x or 6.x (or at least ggated should be from the same FreeBSD version
on which ggatec is running).
For Gbit networks some buffers need to be increased. I use those settings:
kern.ipc.maxsockbuf=16777216
net.inet.tcp.sendspace=8388608
net.inet.tcp.recvspace=8388608
and I use '-S 4194304 -R 4194304' options for both, ggatec and ggated.
Approved by: re (scottl)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
ago in md(4).
Submitted by: Ivan Voras <ivoras@fer.hr>
|
| |
|
| |
|
|
|
|
| |
Inspired by: fjoe
|
| |
|
|
|
|
| |
Provoked by: ru
|
| |
|
|
|
|
|
|
| |
depending on namespace pollution in <sys/stat.h>. struct bintime is
only needed to satisfy leakage of kernel interfaces to userland and
namespace bugs in those interfaces...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This little thing can cause a deadlock, because taste mechanism start
to work after creation of ggate provider and I/O requests are sent from
other classes from the g_event thread, so number of pending events isn't 0.
Now ggatec(8) start second handshake and ggated(8) is trying to open
GEOM provider (for example md(4)) and it can't, because it hangs on
g_waitidle() in g_dev_open(). g_waitidle() cannot finish because
there is a pending read on event queue, and this read can't be
finished, because ggated(8) can't open target device.
GEOM Gate will recover from this deadlock, because requests will
timeout, but it of course isn't the best solution and I don't know
better one for now, so we should avoid opening GEOM providers while
there are pending requests in event queue.
|
|
|
|
| |
Pointed out by: ache, make buildworld
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|