DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Damien Millescamps <damien.millescamps@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 5/7] pci: support multiple PCI regions per device
Date: Wed, 5 Jun 2013 14:33:37 -0700	[thread overview]
Message-ID: <20130605143337.76af91ff@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <51AF7DDB.1070005@6wind.com>

On Wed, 05 Jun 2013 20:05:15 +0200
Damien Millescamps <damien.millescamps@6wind.com> wrote:

> On 06/05/2013 05:49 PM, Stephen Hemminger wrote:
> > On Wed, 05 Jun 2013 16:50:03 +0200
> > Damien Millescamps <damien.millescamps@6wind.com> wrote:
> >
> >> Hi Stephen,
> >>
> >> Overall this patch is very nice. My only comment on this one is why do
> >> you limit the max number of memory resources to 5 ?
> >> The PCI configuration space permits to store up to 6 base addresses.
> >>
> >>> +#define PCI_MEM_RESOURCE 5
> >> Please, can you add a log/comment with your patch, too ?
> >>
> >>
> >> Cheers,
> > Only because I was trying to save some space, and I didn't see any hardware
> > with that many useful regions. Also the kernel UIO driver has some control
> > over which regions get exposed.
> 
> I agree that hardware generally don't use that much BAR for the PCIe.
> However, this is only a matter of 20 to 24 Bytes, so I don't see any
> reason not defining this macro as per the PCI standard value.
> 
> Could you add a commit log and change that so it can be ack'd and pushed
> in the DPDK repository ?
> 
> Thanks,

Go ahead and change the 5 to a 7.
No point in another resend of whole pile.

  reply	other threads:[~2013-06-05 21:33 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 17:12 [dpdk-dev] [PATCH 0/7] Vyatta patches Stephen Hemminger
2013-05-30 17:12 ` [dpdk-dev] [PATCH 1/7] [PATCH 4/8] igb: workaround errata with wthresh on 82576 Stephen Hemminger
2013-06-05 14:22   ` Vincent JARDIN
2013-06-12 10:06     ` [dpdk-dev] [PATCH 1/7] " Thomas Monjalon
2013-05-30 17:12 ` [dpdk-dev] [PATCH 2/7] rte_timer: optimize for empty case Stephen Hemminger
2013-06-05 14:25   ` Vincent JARDIN
2013-06-12 10:07     ` Thomas Monjalon
2013-05-30 17:12 ` [dpdk-dev] [PATCH 3/7] optimize log/panic Stephen Hemminger
2013-06-05 14:34   ` Vincent JARDIN
2013-06-12 10:09     ` Thomas Monjalon
2013-05-30 17:12 ` [dpdk-dev] [PATCH 4/7] eal: support different modules Stephen Hemminger
2013-06-03  8:58   ` Damien Millescamps
2013-06-03 15:41     ` Stephen Hemminger
2013-06-03 16:36       ` Thomas Monjalon
2013-06-03 17:26         ` Stephen Hemminger
2013-06-04  9:17           ` Damien Millescamps
2013-06-03 16:08     ` Antti Kantee
2013-06-03 16:29       ` Thomas Monjalon
2013-06-03 17:25         ` Stephen Hemminger
2013-06-03 18:40         ` Antti Kantee
2013-05-30 17:12 ` [dpdk-dev] [PATCH 5/7] pci: support multiple PCI regions per device Stephen Hemminger
2013-06-03 16:41   ` Thomas Monjalon
2013-06-05 14:50   ` Damien Millescamps
2013-06-05 15:49     ` Stephen Hemminger
2013-06-05 18:05       ` Damien Millescamps
2013-06-05 21:33         ` Stephen Hemminger [this message]
2013-06-18  1:28           ` somnath kotur
2013-07-16  8:53             ` Thomas Monjalon
2013-07-19 16:44               ` Stephen Hemminger
2013-05-30 17:12 ` [dpdk-dev] [PATCH 6/7] igb_uio: pci_block_user_cfg_access is unsafe, remove it Stephen Hemminger
2013-05-30 17:12 ` [dpdk-dev] [PATCH 7/7] eal: add ability to override DPDK syslog parameters Stephen Hemminger
2013-06-05 14:36   ` Vincent JARDIN
2013-06-12 10:18     ` Thomas Monjalon
2013-05-30 22:20 ` [dpdk-dev] [PATCH 0/7] Vyatta patches Thomas Monjalon
2013-05-31  9:29 ` Damien Millescamps
2013-05-31 15:45   ` Stephen Hemminger
2013-05-31 16:44     ` Damien Millescamps
2013-05-31 17:00       ` Stephen Hemminger
2013-06-03 15:22 ` Thomas Monjalon

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=20130605143337.76af91ff@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=damien.millescamps@6wind.com \
    --cc=dev@dpdk.org \
    /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).