All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: FUJITA Tomonori <tomof@acm.org>
Cc: matthew@wil.cx, kay.sievers@vrfy.org,
	James.Bottomley@steeleye.com, jens.axboe@oracle.com,
	hch@infradead.org, jeff@garzik.org, hare@suse.de,
	linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH 3/5] add sg segment limitation info to device structure
Date: Wed, 3 Oct 2007 14:50:19 -0700	[thread overview]
Message-ID: <20071003215019.GF17863@suse.de> (raw)
In-Reply-To: <20071003231034P.tomof@acm.org>

On Wed, Oct 03, 2007 at 11:19:22PM +0900, FUJITA Tomonori wrote:
> On Tue, 2 Oct 2007 09:44:13 -0700
> Greg KH <gregkh@suse.de> wrote:
> 
> > On Tue, Oct 02, 2007 at 09:25:34AM -0600, Matthew Wilcox wrote:
> > > On Tue, Oct 02, 2007 at 05:23:39PM +0200, Kay Sievers wrote:
> > > > Just looking at the number of devices, it seems that allocating it
> > > > dynamically would be the better deal. We allocate the name of every
> > > > kobject dynamically today, so I guess it's fine to do that with the
> > > > DMA data too.
> > > 
> > > But we don't need to allocate it dynamically.  We can embed it in the
> > > pci_dev, eisa_dev, zorro_dev, mca_dev and parisc_device.
> > 
> > But then you run into the issue that James pointed out originally.
> > 
> > Anyway, I don't care which, let's see some patches :)
> 
> How about this (based on James' proposal)?
> 
> - Currently, there are only max_segment_size and segment_boundary_mask
> in struct device_dma_parameters (I'll add segment_boundary_mask
> support later after I finish the iommu part). We'll move more dma
> stuff in struct device (like dma_mask) to struct device_dma_parameters
> later (needs some cleanups before that).
> 
> - New accessors for the dma parameters are added. So we can easily
> change where to place struct device_dma_parameters in the future.
> 
> - the default max_segment_size is set to 64K, same to the block
> layer's default value.
> 
> 
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 37c00f6..c93ebe8 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -1392,6 +1392,13 @@ pci_set_consistent_dma_mask(struct pci_dev *dev, u64 mask)
>  }
>  #endif
>  
> +#ifndef HAVE_ARCH_PCI_SET_DMA_MAX_SEGMENT_SIZE
> +int pci_set_dma_max_seg_size(struct pci_dev *dev, unsigned int size)
> +{
> +	return dma_set_max_seg_size(&dev->dev, size);
> +}
> +#endif
> +
>  /**
>   * pcix_get_max_mmrbc - get PCI-X maximum designed memory read byte count
>   * @dev: PCI device to query
> @@ -1624,6 +1631,7 @@ EXPORT_SYMBOL(pci_clear_mwi);
>  EXPORT_SYMBOL_GPL(pci_intx);
>  EXPORT_SYMBOL(pci_set_dma_mask);
>  EXPORT_SYMBOL(pci_set_consistent_dma_mask);
> +EXPORT_SYMBOL(pci_set_dma_max_seg_size);
>  EXPORT_SYMBOL(pci_assign_resource);
>  EXPORT_SYMBOL(pci_find_parent_resource);
>  EXPORT_SYMBOL(pci_select_bars);

Export the symbol right next to the function, that way the #ifdef
doesn't have to be duplicated.

other than that minor problem, this looks good to me.  James, any
objection to this?

thanks,

greg k-h

      parent reply	other threads:[~2007-10-03 21:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  8:58 [PATCH 3/5] add sg segment limitation info to device structure FUJITA Tomonori
2007-09-26 16:05 ` Greg KH
2007-09-27  0:37   ` FUJITA Tomonori
2007-10-01 23:36   ` James Bottomley
2007-10-02  1:39     ` Matthew Wilcox
2007-10-02  4:22       ` Greg KH
2007-10-02 14:45         ` James Bottomley
2007-10-02 15:02           ` Kay Sievers
2007-10-02 15:05             ` James Bottomley
2007-10-02 15:10               ` Kay Sievers
2007-10-02 15:14                 ` James Bottomley
2007-10-02 15:23                   ` Kay Sievers
2007-10-02 15:25                     ` Matthew Wilcox
2007-10-02 16:44                       ` Greg KH
2007-10-03 14:19                         ` FUJITA Tomonori
2007-10-03 17:57                           ` Jeff Garzik
2007-10-03 21:50                           ` Greg KH [this message]

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=20071003215019.GF17863@suse.de \
    --to=gregkh@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=tomof@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.