Displaying 20 results from an estimated 100 matches similar to: "Can I allocate memory dynamically when enqueue or dequeue? (adding some algorithms in kernel)"
2002 Oct 27
0
Can I use sk_buff->cb in Qdisc?
Hi everybody,
The situation is that I''m creating a queuing
discipline works similar to prio. There''s something I
need to record in each packet, and I wondered that if
I can us the control buffer sk_buff->cb? Though the
comment wrote "It is free to use for every layer.
Please put your private variables there." I''m still
not sure... Please help me to make
2005 Mar 22
1
Mechanism for Enqueue and Dequeue?
I''ve been reading the Linux Advanced Routing & Traffic Control Howto and it''s well put together but I''ve a few questions about the mechanism.
I dont'' think that I''d have any questions if I just wanted to know how to configure the Shaping method but I''m trying to get into the nuts and bolts.
Basically I''m trying to find out the
2005 Sep 30
1
Dequeue
Hi,
Does the ''tc'' tool show dequeue statistics? If so what switches does one
use to see this.
If not which is the best way to see these statistics?
Thanks.
2004 Jun 17
2
[PATCH] (1/4) delay scheduler enqueue always succeeds.
If underlying fifo enqueue fails, return the status not 0.
Same patch should apply to both 2.6 and 2.4
Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
diff -Nru a/net/sched/sch_delay.c b/net/sched/sch_delay.c
--- a/net/sched/sch_delay.c 2004-06-17 15:13:15 -07:00
+++ b/net/sched/sch_delay.c 2004-06-17 15:13:15 -07:00
@@ -69,7 +69,7 @@
sch->stats.bytes += skb->len;
2017 Dec 07
0
[PATCH RFC 0/4] crypto: engine - Permit to enqueue all async requests
On Wed, Dec 06, 2017 at 10:59:47AM +0000, Fabien DESSENNE wrote:
> Hi Corentin,
>
>
> I am fine with this proposal: it is generic enough and I have been able
> to test and run the crypto engine with aead_request without changing any
> single line of code.
>
> This is what I need to be able to send the AEAD extension of the
> stm32-cryp driver (successfully tested
2017 Dec 22
0
[PATCH RFC 1/4] crypto: engine - Permit to enqueue all async requests
On Fri, Dec 22, 2017 at 05:57:24PM +1100, Herbert Xu wrote:
> On Wed, Nov 29, 2017 at 09:41:18AM +0100, Corentin Labbe wrote:
> > The crypto engine could actually only enqueue hash and ablkcipher request.
> > This patch permit it to enqueue any type of crypto_async_request.
> >
> > Signed-off-by: Corentin Labbe <clabbe.montjoie at gmail.com>
>
> This is
2017 Dec 22
1
[PATCH RFC 1/4] crypto: engine - Permit to enqueue all async requests
On Fri, Dec 22, 2017 at 09:41:48AM +0100, Corentin Labbe wrote:
>
> It's you that was suggesting using crypto_async_request:
> https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1474434.html
> "The only wart with this scheme is that the drivers end up seeing
> struct crypto_async_request and will need to convert that to the
> respective request types but I
2018 Feb 15
0
[PATCH v2 0/6] crypto: engine - Permit to enqueue all async requests
On Fri, Jan 26, 2018 at 08:15:28PM +0100, Corentin Labbe wrote:
> Hello
>
> The current crypto_engine support only ahash and ablkcipher request.
> My first patch which try to add skcipher was Nacked, it will add too many functions
> and adding other algs(aead, asymetric_key) will make the situation worst.
>
> This patchset remove all algs specific stuff and now only process
2017 Dec 22
2
[PATCH RFC 1/4] crypto: engine - Permit to enqueue all async requests
On Wed, Nov 29, 2017 at 09:41:18AM +0100, Corentin Labbe wrote:
> The crypto engine could actually only enqueue hash and ablkcipher request.
> This patch permit it to enqueue any type of crypto_async_request.
>
> Signed-off-by: Corentin Labbe <clabbe.montjoie at gmail.com>
This is going the wrong way. We do not want to expose any of the
base types such as crypto_alg,
2017 Dec 22
2
[PATCH RFC 1/4] crypto: engine - Permit to enqueue all async requests
On Wed, Nov 29, 2017 at 09:41:18AM +0100, Corentin Labbe wrote:
> The crypto engine could actually only enqueue hash and ablkcipher request.
> This patch permit it to enqueue any type of crypto_async_request.
>
> Signed-off-by: Corentin Labbe <clabbe.montjoie at gmail.com>
This is going the wrong way. We do not want to expose any of the
base types such as crypto_alg,
2017 Dec 06
0
[PATCH RFC 0/4] crypto: engine - Permit to enqueue all async requests
Hi Corentin,
I am fine with this proposal: it is generic enough and I have been able
to test and run the crypto engine with aead_request without changing any
single line of code.
This is what I need to be able to send the AEAD extension of the
stm32-cryp driver (successfully tested with your engine upgrade proposal).
I have also tested the stm32-hash patch.
Note that stm32-cryp (new
2018 Feb 16
1
[PATCH v2 0/6] crypto: engine - Permit to enqueue all async requests
On Thu, Feb 15, 2018 at 11:51:00PM +0800, Herbert Xu wrote:
> On Fri, Jan 26, 2018 at 08:15:28PM +0100, Corentin Labbe wrote:
> > Hello
> >
> > The current crypto_engine support only ahash and ablkcipher request.
> > My first patch which try to add skcipher was Nacked, it will add too many functions
> > and adding other algs(aead, asymetric_key) will make the
2017 Nov 03
0
[PATCH v17 3/6] mm/balloon_compaction.c: split balloon page allocation and enqueue
From: "Michael S. Tsirkin" <mst.redhat.com>
fill_balloon doing memory allocations under balloon_lock
can cause a deadlock when leak_balloon is called from
virtballoon_oom_notify and tries to take same lock.
To fix, split page allocation and enqueue and do allocations outside
the lock.
Here's a detailed analysis of the deadlock by Tetsuo Handa:
In leak_balloon(),
2002 Oct 08
1
[tcng] tcc specify device
hi,
i was looking tcc --help, there seems to be no way to tell tcc to generate output only for specified device i.e.
tcc -device eth0
m''I mistaken ?
thanx
raptor
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
2017 Dec 07
0
[PATCH RFC 1/4] crypto: engine - Permit to enqueue all async requests
On Wed, Dec 06, 2017 at 11:02:23AM +0000, Fabien DESSENNE wrote:
>
>
> On 29/11/17 09:41, Corentin Labbe wrote:
> > The crypto engine could actually only enqueue hash and ablkcipher request.
> > This patch permit it to enqueue any type of crypto_async_request.
> >
> > Signed-off-by: Corentin Labbe <clabbe.montjoie at gmail.com>
> > ---
> >
2017 Nov 29
0
[PATCH RFC 1/4] crypto: engine - Permit to enqueue all async requests
The crypto engine could actually only enqueue hash and ablkcipher request.
This patch permit it to enqueue any type of crypto_async_request.
Signed-off-by: Corentin Labbe <clabbe.montjoie at gmail.com>
---
crypto/crypto_engine.c | 188 +++++++++++-------------------------------------
include/crypto/engine.h | 46 +++++-------
2 files changed, 60 insertions(+), 174 deletions(-)
diff
2003 Dec 02
2
forwarding in tcng
Hi!
I am learning tcng without having experiance of tc and I am trying to
build something that shall schedule traffic dependent on the value in the
IPv4 packets ip_ttl field.
I have read the tcng reference manual and cannot find information about
forwarding. Is it possible to farward packets from ingress to egress
without sending them upwards in layers?
2002 Oct 10
2
tcng version 8z
... is on SourceForge, http://tcng.sourceforge.net/#src
Besides a bunch of bug fixes, this release also contains a
greatly improved version of the comtc utility that copies
comments from the tcng source to tcc''s "tc" output.
There are a few infrastructure changes to make comtc work
smoothly:
- tcc''s -E option is now called -Wexperror or -Wexppostopt,
respectively
2003 Mar 13
4
howto mark packet''s dscp value
Dear all
can anyone tell me how to mark packet''s DSCP value using tc?
Thanks.
Regards,
philip
--
Hong Kong IP Multicast Initiative (HKIPMI)
Department of Information Engineering
The Chinese University of Hong Kong
Phone : 2603 5240
Fax : 2603 5032
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
2002 Oct 20
4
Problems patching kernel 2.4.19-r9
A question about the tc binary and diff file that are
included in htb3.6-020525.tgz. I can''t seem to patch tc
in the source tree, and that has made me hesitate to
alternatively substitute the native /usr/sbin/tc for
the binary supplied with the patch materials. I''m
running kernel 2.4.19-r9, and when I run
xingu:/usr/src/linux #patch -p1 --dry-run <
../htb3.6.tc.diff
the