DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "François-Frédéric Ozog" <ff@ozog.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Bit spinlocks in DPDK
Date: Thu, 19 Dec 2013 17:41:08 +0100	[thread overview]
Message-ID: <201312191741.08477.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <01d001cef375$7167e300$5437a900$@com>

07/12/2013 18:54, François-Frédéric Ozog :
> > De Thomas Monjalon
> > 06/12/2013 14:12, Pashupati Kumar :
> > > I am looking for spinlocks that use a single bit (bit 31) of a 32 bit
> > > word for locking. The rest of the bits in the word are left
> > > undisturbed.  This enables more compact data structures as only 1 bit
> > > is consumed for the lock.
> > 
> > Oh yes, like test_and_set_bit_lock() in Linux:
> > 	http://lxr.free-electrons.com/source/arch/ia64/include/asm/bitops.h?v=3.12#L205
> > 
> > I think that a patch would be appreciated :)
> 
> I assume you mean the x64 version, not the ia64:
> http://lxr.free-electrons.com/source/arch/x86/include/asm/bitops.h.

Yes you're right.

> What is the policy to share a sample program: inline in a mail or as a
> attachment?

Inline should be fine. It allows to comment.

> What is the policy to submit a patch?

It's now explained here:
http://dpdk.org/dev#send

-- 
Thomas

  reply	other threads:[~2013-12-19 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 21:04 Pashupati Kumar
2013-12-06 22:02 ` Thomas Monjalon
2013-12-06 22:12   ` Pashupati Kumar
2013-12-06 22:24     ` Thomas Monjalon
2013-12-06 22:54       ` Pashupati Kumar
2013-12-07 17:54       ` François-Frédéric Ozog
2013-12-19 16:41         ` Thomas Monjalon [this message]
2013-12-20 15:39         ` Thomas Monjalon
2013-12-20 16:00           ` François-Frédéric Ozog
2013-12-20 16:36             ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201312191741.08477.thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ff@ozog.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).