The submission of man to His Creator is the essence of Islam. The name
"Islam" is chosen by God (Allah) and not by man. It is the same
unifying Message revealed to all the Prophets and Messengers by Allah
and which they spread amongst their respective nations. In its Final
form it wa
On Oct 15, 2012, at 09:08 , John Baldwin wrote:
> On Friday, October 12, 2012 12:13:11 pm John Baldwin wrote:
>> Back in 2001 FreeBSD added a hack to strip TCP options from retransmitted
>> SYNs
>> starting with the 3rd SYN in this block in tcp_timer.c:
>>
>> /*
>> * Disable rfc132
The reason why I've started moving net80211 and ath _away_ from using
direct dispatch (for now) and to using a taskqueue for TX (and RX) is
because it's too freaking annoying right now to deal with all the
crazy long-held locks to guarantee consistency between multiple
transmitting threads.
Consid
On Mon, Oct 15, 2012 at 12:29 PM, Gleb Smirnoff wrote:
> To me this unlock/lock looks like a legacy from times, when the driver
> had a single mutex for both TX and RX parts.
>
> And removing this re-locking in foo_rxeof() was one of the aims for separate
> TX/RX locking.
>
> Really, lurking throu
On Monday, October 15, 2012 12:32:10 pm Gleb Smirnoff wrote:
> On Mon, Oct 15, 2012 at 09:04:27AM -0400, John Baldwin wrote:
> J> > 3) in practice taskqueue routine is a nightmare for many people since
> J> > there is no way to stop "kernel {ix0 que}" thread eating 100% cpu after
> J> > some traf
On Mon, Oct 15, 2012 at 9:58 AM, Gleb Smirnoff wrote:
> On Mon, Oct 15, 2012 at 09:39:24AM -0700, Jack Vogel wrote:
> J> > To me this unlock/lock looks like a legacy from times, when the driver
> J> > had a single mutex for both TX and RX parts.
> J> >
> J> > And removing this re-locking in foo_r
On Mon, Oct 15, 2012 at 09:39:24AM -0700, Jack Vogel wrote:
J> > To me this unlock/lock looks like a legacy from times, when the driver
J> > had a single mutex for both TX and RX parts.
J> >
J> > And removing this re-locking in foo_rxeof() was one of the aims for
J> > separate
J> > TX/RX locking.
J
On 15.10.2012 20:39, Jack Vogel wrote:
I did not want to add it back, there were problems that constrained me
to do so, although its
been some time, I'd be happy to do some testing again without and see.
We've got more than hundred routers/firewalls running under heavy load
without this lock
On Mon, Oct 15, 2012 at 9:29 AM, Gleb Smirnoff wrote:
> On Sat, Oct 13, 2012 at 09:49:21PM +0400, Alexander V. Chernikov wrote:
> A> Packets receiving code for both ixgbe and if_igb looks like the
> following:
> A> ixgbe_msix_que
> A>
> A> -- ixgbe_rxeof()
> A> {
> A>IXGBE_RX_LOCK(rxr
On Mon, Oct 15, 2012 at 09:04:27AM -0400, John Baldwin wrote:
J> > 3) in practice taskqueue routine is a nightmare for many people since
J> > there is no way to stop "kernel {ix0 que}" thread eating 100% cpu after
J> > some traffic burst happens: once it is called it starts to schedule
J> > itse
On Sat, Oct 13, 2012 at 09:49:21PM +0400, Alexander V. Chernikov wrote:
A> Packets receiving code for both ixgbe and if_igb looks like the following:
A> ixgbe_msix_que
A>
A> -- ixgbe_rxeof()
A> {
A>IXGBE_RX_LOCK(rxr);
A> while
A> {
A> get_packet;
A>
A>
On Friday, October 12, 2012 12:13:11 pm John Baldwin wrote:
> Back in 2001 FreeBSD added a hack to strip TCP options from retransmitted
> SYNs
> starting with the 3rd SYN in this block in tcp_timer.c:
>
> /*
>* Disable rfc1323 if we haven't got any response to
>* our third
On Monday, October 15, 2012 10:10:40 am Alexander V. Chernikov wrote:
> On 13.10.2012 23:24, Jack Vogel wrote:
> > On Sat, Oct 13, 2012 at 11:22 AM, Luigi Rizzo wrote:
>
> >>
> >> one option could be (same as it is done in the timer
> >> routine in dummynet) to build a list of all the packets
> >
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.o
On 13.10.2012 23:24, Jack Vogel wrote:
On Sat, Oct 13, 2012 at 11:22 AM, Luigi Rizzo wrote:
one option could be (same as it is done in the timer
routine in dummynet) to build a list of all the packets
that need to be sent to if_input(), and then call
if_input with the entire list outside the
Hello list!
I have FreeBSD 8.2-p3 and observe a strange behaviour
sysctl -a | g bce.3|g -vE '(%|stat)'; echo; sleep 10; sysctl -a | g bce.3|
g -vE '(%|stat)'; echo; netstat -m
dev.bce.3.l2fhdr_error_count: 0
dev.bce.3.mbuf_alloc_failed_count: 2098854
dev.bce.3.mbuf_frag_count: 2655285
dev.bce.3
16 matches
Mail list logo
