In message <516c71bc.4000...@freebsd.org>, Alexander Motin writes:
>On 15.04.2013 23:43, Poul-Henning Kamp wrote:
>> In message <516c515a.9090...@freebsd.org>, Alexander Motin writes:
>>
>> For tuning anything on a non-ridiculous SSD device or modern
>> harddisks, it will be useless because of the
On 15.04.2013 23:43, Poul-Henning Kamp wrote:
In message <516c515a.9090...@freebsd.org>, Alexander Motin writes:
I propose to switch that
statistics from using binuptime() to getbinuptime() to solve the problem
globally.
No objections here, but I wonder if you were able to compare the result
In message <516c515a.9090...@freebsd.org>, Alexander Motin writes:
>>> I propose to switch that
>>> statistics from using binuptime() to getbinuptime() to solve the problem
>>> globally.
>> No objections here, but I wonder if you were able to compare the results
>> somehow before and after the ch
Hello!
A few weeks ago, I ran into problem, which related to SystemV IPC.
More than 20 processes attached to a segment shared queue. Process-initiator for
create segment was killed, as process which was accessed to segment
last. Segment didn't free memory, but tagged it as SHMSEG_REMOVED as
the res
On 4/15/2013 5:41 AM, Hans Petter Selasky wrote:
Hi,
What does dmesg say about your printer.
Is cups hooked up the correct /dev/uxxx device ?
--HPS
Here's what I got the last time I plugged it in.
Apr 13 07:38:17 jri root: Unknown USB device: vendor 0x040a product
0x4043 bus uhub7
Apr 13
On Mon, Apr 15, 2013 at 09:37:30PM +0200, Pawel Jakub Dawidek wrote:
> On Mon, Apr 15, 2013 at 10:18:15PM +0300, Konstantin Belousov wrote:
> > On Mon, Apr 15, 2013 at 08:42:03PM +0200, Pawel Jakub Dawidek wrote:
> > > On a mostly unrelated note when two threads (T0 and T1) call get*time()
> > > on
On Mon, Apr 15, 2013 at 10:18:15PM +0300, Konstantin Belousov wrote:
> On Mon, Apr 15, 2013 at 08:42:03PM +0200, Pawel Jakub Dawidek wrote:
> > On a mostly unrelated note when two threads (T0 and T1) call get*time()
> > on two different cores, but T0 does that a bit earlier is it possible
> > that
On Mon, Apr 15, 2013 at 08:42:03PM +0200, Pawel Jakub Dawidek wrote:
> On a mostly unrelated note when two threads (T0 and T1) call get*time()
> on two different cores, but T0 does that a bit earlier is it possible
> that T0 can get later time than T1?
Define earlier first.
If you have taken suff
On 15.04.2013 21:42, Pawel Jakub Dawidek wrote:
On Sat, Apr 13, 2013 at 12:59:49PM +0300, Alexander Motin wrote:
Hi.
It is long known that collecting disk and GEOM statistics may cause
significant processing overhead under high IOPS. On my recent high-IOPS
benchmarks performance difference was
On Sat, Apr 13, 2013 at 12:59:49PM +0300, Alexander Motin wrote:
> Hi.
>
> It is long known that collecting disk and GEOM statistics may cause
> significant processing overhead under high IOPS. On my recent high-IOPS
> benchmarks performance difference was reaching three times! Last time
> situ
Hello list.
We currently have VLAHWFILTER functionality allowing underlying
physical/virtual interfaces to be aware of vlans stacked on them.
However, this knowledge is only used to program NIC hw filter (or to
broadcast to member ifaces in lagg case).
Proposed idea is to save vlan ifp pointer i
On 04/14/13 00:45, Joshua Isom wrote:
I've got my printer to finally work, now that I got around to hooking it
up again and trying. It's a Kodak AiO, and there's a driver that's been
around for a few years and works under Linux. It doesn't work properly
under FreeBSD, or a Debian/kFreeBSD jail,
12 matches
Mail list logo
