There are a number of other tweaks that can assist in improving performance for Openswan that are not related to the startup time.
Depending on the plutodebug=
and klipsdebug=
settings, you might be logging so much data through syslog that the disk activity actually becomes a big limiting factor. In some benchmarks, we even found the minimal logging (plutodebug=none
) to cause a possible bottleneck. A feature is planned to enable a minimal logging level that avoids this bottleneck. Ensure you are using 32-bit I/O on the disk where your logs are written. You can verify this, for /dev/hda
in our example, using:
# hdparm -c /dev/hda
/dev/hda: IO_support = 0 (default 16-bit)
Here the 32-bit IO support is not enabled. Use the following command to enable it:
# hdparm -c 1 /dev/hda
/dev/hda: setting 32-bit IO_support flag to 1 IO_support = 1 (32-bit)
Similar commands can be used to view and set DMA hard disk transfers, but with...